From: "Michael Kubacki" <mikuback@linux.microsoft.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: Split up MdeModulePkg and CryptoPkg CodeQL CI checks
Date: Mon, 3 Apr 2023 20:56:14 -0400 [thread overview]
Message-ID: <293b2465-cd2a-6e43-812a-fbea05082e6c@linux.microsoft.com> (raw)
In-Reply-To: <CO1PR11MB4929E88197129E0396763FA8D28C9@CO1PR11MB4929.namprd11.prod.outlook.com>
Hi Mike,
The changes in this PR look reasonable
https://github.com/tianocore/edk2/pull/4233 if you'd like to send a patch.
Thanks,
Michael
On 4/1/2023 6:53 PM, Kinney, Michael D wrote:
> Hi Michael,
>
> On the Azure Piplines side, the same 2 packages have the longest
> build time. The DEBUG and RELEASE builds take about the same
> time each. The NO-TARGET and NOOPT combined are less than
> DEBUG or RELEASE.
>
> stuart_ci_build -c .pytool/CISettings.py -p CryptoPkg -t DEBUG,RELEASE,NO-TARGET,NOOPT -a IA32,X64,ARM,AARCH64,RISCV64,LOONGARCH64 TOOL_CHAIN_TAG=GCC5
>
> Could we split the CryptoPkg and MdeModulePkg jobs into 3 jobs each?
> * DEBUG
> * RELEASE
> * NO-TARGET, NOOPT
>
> Alternatively, split into 2 jobs
>
> * DEBUG, NO-TARGET
> * RELEASE, NOOPT
>
> Thanks,
>
> Mike
>
>
>> -----Original Message-----
>> From: Kinney, Michael D <michael.d.kinney@intel.com>
>> Sent: Saturday, April 1, 2023 3:31 PM
>> To: devel@edk2.groups.io; Michael Kubacki <mikuback@linux.microsoft.com>
>> Cc: Kinney, Michael D <michael.d.kinney@intel.com>
>> Subject: Split up MdeModulePkg and CryptoPkg CodeQL CI checks
>>
>> Hi Michael,
>>
>> I am looking at the CI agent execution times since we resolved
>> several issued the last few days.
>>
>> We have CodeQL running in GitHub Actions and the rest of the
>> Checks running in Azure Pipelines.
>>
>> Looking at only CodeQL, I see that the 2 longest jobs are
>> on the MdeModulePkg and CryptoPkg and they build for both
>> IA32 and X64 to get 32-bit and 64-bit coverage.
>>
>> * stuart_ci_build -c .pytool/CISettings.py -p CryptoPkg -t DEBUG -a IA32,X64 TOOL_CHAIN_TAG=VS2019
>> * stuart_ci_build -c .pytool/CISettings.py -p MdeModulePkg -t DEBUG -a IA32,X64 TOOL_CHAIN_TAG=VS2019
>>
>> Is it possible to split these two jobs into 4 jobs to check
>> IA32 and X64 independently?
>>
>> * stuart_ci_build -c .pytool/CISettings.py -p CryptoPkg -t DEBUG -a IA32 TOOL_CHAIN_TAG=VS2019
>> * stuart_ci_build -c .pytool/CISettings.py -p CryptoPkg -t DEBUG -a X64 TOOL_CHAIN_TAG=VS2019
>> * stuart_ci_build -c .pytool/CISettings.py -p MdeModulePkg -t DEBUG -a IA32 TOOL_CHAIN_TAG=VS2019
>> * stuart_ci_build -c .pytool/CISettings.py -p MdeModulePkg -t DEBUG -a X64 TOOL_CHAIN_TAG=VS2019
>>
>> Thanks,
>>
>> Mike
>>
>
prev parent reply other threads:[~2023-04-04 0:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 22:31 Split up MdeModulePkg and CryptoPkg CodeQL CI checks Michael D Kinney
2023-04-01 22:53 ` Michael D Kinney
2023-04-04 0:56 ` Michael Kubacki [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=293b2465-cd2a-6e43-812a-fbea05082e6c@linux.microsoft.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox