public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael Kubacki" <mikuback@linux.microsoft.com>
To: devel@edk2.groups.io, michael.d.kinney@intel.com
Cc: Sean Brogan <sean.brogan@microsoft.com>,
	Liming Gao <gaoliming@byosoft.com.cn>
Subject: Re: [edk2-devel] [Patch 0/2] Balance CI Execution Times
Date: Tue, 4 Apr 2023 09:55:47 -0400	[thread overview]
Message-ID: <6a8a83c3-ae9f-5acd-d370-8457132328d1@linux.microsoft.com> (raw)
In-Reply-To: <20230404042441.130-1-michael.d.kinney@intel.com>

For the series:

Reviewed-by: Michael Kubacki <michael.kubacki@microsoft.com>

On 4/4/2023 12:24 AM, Michael D Kinney wrote:
> MdeModulePkg and CryptoPkg have double the CodeQL analysis
> time of all other packages.  Split these packages up to perform
> separate analysis of IA32 and X64.
> 
> CryptoPkg has double the build time of all other packages.
> Split CryptoPkg up matching the style applied to MdeModulePkg.
> 
> Cc: Sean Brogan <sean.brogan@microsoft.com>
> Cc: Michael Kubacki <mikuback@linux.microsoft.com>
> Cc: Liming Gao <gaoliming@byosoft.com.cn>
> Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com>
> 
> Michael D Kinney (2):
>    .github.workflows: Split MdeModulePkg and CryptoPkg analysis
>    .azurepilelines/templates: Split CryptoPkg builds
> 
>   .../templates/pr-gate-build-job.yml           |  7 +-
>   .github/workflows/codeql-analysis.yml         | 64 ++++++++++++-------
>   2 files changed, 47 insertions(+), 24 deletions(-)
> 

  parent reply	other threads:[~2023-04-04 13:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-04  4:24 [Patch 0/2] Balance CI Execution Times Michael D Kinney
2023-04-04  4:24 ` [Patch 1/2] .github.workflows: Split MdeModulePkg and CryptoPkg analysis Michael D Kinney
2023-04-04  4:24 ` [Patch 2/2] .azurepilelines/templates: Split CryptoPkg builds Michael D Kinney
2023-04-04 13:55 ` Michael Kubacki [this message]
2023-04-04 17:58   ` [edk2-devel] [Patch 0/2] Balance CI Execution Times Michael D Kinney

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=6a8a83c3-ae9f-5acd-d370-8457132328d1@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