From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"rebecca@bsdio.com" <rebecca@bsdio.com>,
Gerd Hoffmann <kraxel@redhat.com>
Cc: Leif Lindholm <quic_llindhol@quicinc.com>,
Ard Biesheuvel <ardb@kernel.org>,
Pedro Falcato <pedro.falcato@gmail.com>,
"Gao, Liming" <gaoliming@byosoft.com.cn>,
Oliver Smith-Denny <osd@smith-denny.com>,
"Jiang, Guomin" <guomin.jiang@intel.com>,
"Lu, Xiaoyu1" <xiaoyu1.lu@intel.com>,
"Wang, Jian J" <jian.j.wang@intel.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
"Feng, Bob C" <bob.c.feng@intel.com>,
"Andrew Fish" <afish@apple.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: 回复: [edk2-devel] [PATCH v2 00/13] BaseTools,CryptoPkg,MdePkg,OvmfPkg: Delete CLANG35,CLANG38,GCC48,GCC49, rename GCC5 to GCC, update CLANGDWARF, delete VS 2008-2013, EBC
Date: Mon, 3 Apr 2023 19:42:36 +0000 [thread overview]
Message-ID: <CO1PR11MB49296396116AF93DE3652732D2929@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <7d6a6e15-f8da-4cee-bd52-d546052bf03b@bsdio.com>
Rebecca,
I have a test PR running that splits up CodeQL analysis
and builds to attempt to balance the execution times.
https://github.com/tianocore/edk2/pull/4233
GitHub Actions CodeQL:
* Max job time ~21 minutes
* Total Action Time ~31 minutes
Azure Pipelines Builds:
* Max job time ~32 minutes
* Total job time ~36 minutes
This is a reduction of about 6 minutes from other PRs
in recent history, so may be worth checkin in.
There is also a dependency on the total number of agents.
If we have more jobs than agents, them they get queued
up and will not run until another job completes.
Mike
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Rebecca Cran
> Sent: Monday, April 3, 2023 7:28 AM
> To: Gerd Hoffmann <kraxel@redhat.com>
> Cc: Leif Lindholm <quic_llindhol@quicinc.com>; Ard Biesheuvel <ardb@kernel.org>; devel@edk2.groups.io; Pedro Falcato
> <pedro.falcato@gmail.com>; Gao, Liming <gaoliming@byosoft.com.cn>; Oliver Smith-Denny <osd@smith-denny.com>; Jiang, Guomin
> <guomin.jiang@intel.com>; Lu, Xiaoyu1 <xiaoyu1.lu@intel.com>; Wang, Jian J <jian.j.wang@intel.com>; Yao, Jiewen
> <jiewen.yao@intel.com>; Ard Biesheuvel <ardb+tianocore@kernel.org>; Justen, Jordan L <jordan.l.justen@intel.com>; Feng,
> Bob C <bob.c.feng@intel.com>; Andrew Fish <afish@apple.com>; Kinney, Michael D <michael.d.kinney@intel.com>
> Subject: Re: 回复: [edk2-devel] [PATCH v2 00/13] BaseTools,CryptoPkg,MdePkg,OvmfPkg: Delete CLANG35,CLANG38,GCC48,GCC49,
> rename GCC5 to GCC, update CLANGDWARF, delete VS 2008-2013, EBC
>
> On 4/3/23 8:08 AM, Gerd Hoffmann wrote:
> > So you want gcc-6 specifically or just an older version instead of
> > latest? I could try add a RHEL-8 container (which ships gcc-8).
>
> I'd want the oldest version that we support, so we know when we add
> incompatible code.
>
> From Pedro's reply, it sounds like that'll be gcc 5 once we add
> -std=c++11 to tools_def.txt.template.
>
>
> > Well, I've wondered whenever it makes sense to do _less_ stuff in
> > parallel, to get down the constant overhead (clone repos etc).
> > Especially with a limit on parallel jobs that could be faster
> > in the end ...
>
> Maybe a combination? For example one task that I think could do with
> being split up to run in parallel is the following:
>
> stuart_ci_build -c .pytool/CISettings.py -p CryptoPkg -t
> DEBUG,RELEASE,NO-TARGET,NOOPT -a IA32,X64 TOOL_CHAIN_TAG=VS2019
>
> (from
> https://dev.azure.com/tianocore/edk2-ci/_build/results?buildId=85605&view=logs&j=c0929384-5a08-5c0f-b36d-
> 6f51b6b81732&t=f12d60be-1b97-57a4-b1ea-5aae2f026d4f)
>
>
> It shows two tasks taking 13 minutes each.
>
>
> --
>
> Rebecca Cran
>
>
>
>
>
>
next prev parent reply other threads:[~2023-04-03 19:42 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 17:30 [PATCH v2 00/13] BaseTools,CryptoPkg,MdePkg,OvmfPkg: Delete CLANG35,CLANG38,GCC48,GCC49, rename GCC5 to GCC, update CLANGDWARF, delete VS 2008-2013, EBC Rebecca Cran
2023-03-28 17:30 ` [PATCH v2 01/13] OvmfPkg: Replace static struct initialization with ZeroMem call Rebecca Cran
2023-03-28 22:40 ` Yao, Jiewen
2023-03-28 22:45 ` Michael D Kinney
2023-03-28 17:31 ` [PATCH v2 02/13] CryptoPkg: Add CLANGDWARF and remove CLANG35 and CLANG38 compiler flags Rebecca Cran
2023-03-28 17:31 ` [PATCH v2 03/13] BaseTools: Update CLANGDWARF toolchain and remove CLANG35 and CLANG38 Rebecca Cran
2023-03-29 3:46 ` [edk2-devel] " Guo, Gua
[not found] ` <1750C725F99FA0C2.29160@groups.io>
2023-03-29 9:24 ` Guo, Gua
2023-03-28 17:31 ` [PATCH v2 04/13] BaseTools: Remove VS2008, 2010, 2012 and 2013 toolchain definitions Rebecca Cran
2023-03-28 17:31 ` [PATCH v2 05/13] BaseTools: Remove VS2008-VS2013 remnants Rebecca Cran
2023-03-28 17:31 ` [PATCH v2 06/13] MdePkg: " Rebecca Cran
2023-03-28 17:31 ` [PATCH v2 07/13] edksetup.bat: " Rebecca Cran
2023-03-28 17:31 ` [PATCH v2 08/13] BaseTools: Remove unused IPHONE_TOOLS and SOURCERY_CYGWIN_TOOLS defs Rebecca Cran
2023-03-28 17:31 ` [PATCH v2 09/13] BaseTools: Remove EBC (EFI Byte Code) compiler definitions Rebecca Cran
2023-03-28 17:31 ` [PATCH v2 10/13] OvmfPkg: Use Xcode5 version of CpuExceptionHandlerLib for CLANGDWARF Rebecca Cran
2023-03-28 17:31 ` [PATCH v2 11/13] Delete GCC48 and GCC49 toolchains and rename GCC5 to GCC Rebecca Cran
2023-03-28 17:31 ` [PATCH v2 12/13] BaseTools: Remove unused CYGWIN_ defines from tools_def.txt.template Rebecca Cran
2023-03-28 17:31 ` [PATCH v2 13/13] Bump tools_def.txt VERSION to 3.0 Rebecca Cran
2023-03-28 17:57 ` [PATCH v2 00/13] BaseTools,CryptoPkg,MdePkg,OvmfPkg: Delete CLANG35,CLANG38,GCC48,GCC49, rename GCC5 to GCC, update CLANGDWARF, delete VS 2008-2013, EBC Ard Biesheuvel
2023-03-28 18:01 ` Rebecca Cran
2023-03-28 18:12 ` [edk2-devel] " Ard Biesheuvel
2023-03-29 10:21 ` Rebecca Cran
2023-03-29 10:30 ` Ard Biesheuvel
2023-03-29 1:19 ` 回复: " gaoliming
2023-03-29 7:39 ` Ard Biesheuvel
2023-03-29 10:20 ` Rebecca Cran
2023-03-29 11:28 ` Leif Lindholm
2023-03-29 11:53 ` Ard Biesheuvel
2023-04-02 15:41 ` 回复: " Rebecca Cran
2023-04-02 16:36 ` Ard Biesheuvel
2023-04-02 16:42 ` Michael D Kinney
2023-04-02 18:38 ` Pedro Falcato
2023-04-02 21:50 ` Rebecca Cran
2023-04-03 11:30 ` Gerd Hoffmann
2023-04-03 11:33 ` Rebecca Cran
2023-04-03 11:39 ` Gerd Hoffmann
2023-04-03 11:55 ` Ard Biesheuvel
2023-04-03 12:15 ` Leif Lindholm
2023-04-03 12:26 ` Rebecca Cran
2023-04-03 13:44 ` Pedro Falcato
2023-04-03 13:54 ` Rebecca Cran
2023-04-03 14:08 ` Gerd Hoffmann
2023-04-03 14:27 ` Rebecca Cran
2023-04-03 19:42 ` Michael D Kinney [this message]
2023-04-03 19:54 ` Rebecca Cran
2023-04-03 20:23 ` Michael D Kinney
2023-04-03 13:04 ` Ard Biesheuvel
2023-04-03 13:27 ` Michael D Kinney
2023-04-03 13:43 ` Ard Biesheuvel
2023-04-04 1:31 ` 回复: " gaoliming
2023-04-04 15:49 ` Rebecca Cran
2023-04-04 15:57 ` Pedro Falcato
2023-04-04 16:32 ` Leif Lindholm
2023-04-04 17:00 ` Rebecca Cran
2023-04-04 17:45 ` Michael D Kinney
2023-04-04 17:48 ` Rebecca Cran
2023-04-04 17:52 ` Michael D Kinney
2023-04-04 17:57 ` Pedro Falcato
2023-04-04 18:03 ` Rebecca Cran
2023-04-04 18:26 ` Ard Biesheuvel
2023-04-04 18:29 ` Michael D Kinney
2023-04-04 18:36 ` Rebecca Cran
2023-04-05 10:21 ` Ard Biesheuvel
2023-04-06 0:57 ` 回复: " gaoliming
2023-04-06 2:49 ` Rebecca Cran
2023-04-06 7:32 ` Ard Biesheuvel
2023-04-06 9:19 ` Marcin Juszkiewicz
2023-03-29 12:20 ` Ard Biesheuvel
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=CO1PR11MB49296396116AF93DE3652732D2929@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