public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <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
Date: Sat, 1 Apr 2023 22:31:13 +0000	[thread overview]
Message-ID: <CO1PR11MB49293DBACBD9483BB17A9873D28C9@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)

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



             reply	other threads:[~2023-04-01 22:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-01 22:31 Michael D Kinney [this message]
2023-04-01 22:53 ` Split up MdeModulePkg and CryptoPkg CodeQL CI checks Michael D Kinney
2023-04-04  0:56   ` Michael Kubacki

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=CO1PR11MB49293DBACBD9483BB17A9873D28C9@CO1PR11MB4929.namprd11.prod.outlook.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