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

["Rebecca Cran" <rebecca@bsdio.com>]

I wonder if it might be possible to get the total time to be under 10 
minutes by adding more agents?


-- 

Rebecca Cran


On 4/3/23 1:42 PM, Kinney, Michael D wrote:
> 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
>>
>>
>>
>>
>> 
>>