From: "Michael Kubacki" <mikuback@linux.microsoft.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Sean Brogan <sean.brogan@microsoft.com>,
Bret Barkelew <Bret.Barkelew@microsoft.com>,
Liming Gao <gaoliming@byosoft.com.cn>,
Michael Kubacki <michael.kubacki@microsoft.com>
Subject: Re: [edk2-devel] [Patch 1/1] .azurepipelines/templates: Update max pipeline job time to 2 hours
Date: Tue, 23 Nov 2021 21:01:38 -0500 [thread overview]
Message-ID: <fed59a8a-5710-0610-5acf-b4c4a92c73dd@linux.microsoft.com> (raw)
In-Reply-To: <CO1PR11MB492908C4568CE2400DB7C42CD2619@CO1PR11MB4929.namprd11.prod.outlook.com>
I wouldn't expect it to extend past 1 hour that often either. An
occasional audit sounds good though.
Do you think a BZ could be filed to track the ECC optimization work? I
didn't see anything obvious with a quick search.
Thanks,
Michael
On 11/23/2021 7:54 PM, Kinney, Michael D wrote:
> Hi Michael,
>
> I would like to see some optimization work applied to the ECC tool to see if
> we can reduce the time that tool requires. If we find some easy improvements
> that allow larger patch series to complete in 60 minutes, then I am in favor
> of reducing back down to 60 minutes.
>
> Unless we actually see jobs running more than 60 minutes or hitting the 120
> minute timeout, I do not see this patch causing problems. We can do an audit
> of PRs once is a while to see what the job execution times are.
>
> If we do want to reduce, it will have to be a separate patch after uncrustify
> set of PRs is applied.
>
> Mike
>
>> -----Original Message-----
>> From: Michael Kubacki <mikuback@linux.microsoft.com>
>> Sent: Tuesday, November 23, 2021 4:49 PM
>> To: devel@edk2.groups.io; Kinney, Michael D <michael.d.kinney@intel.com>
>> Cc: Sean Brogan <sean.brogan@microsoft.com>; Bret Barkelew <Bret.Barkelew@microsoft.com>; Liming Gao
>> <gaoliming@byosoft.com.cn>; Michael Kubacki <michael.kubacki@microsoft.com>
>> Subject: Re: [edk2-devel] [Patch 1/1] .azurepipelines/templates: Update max pipeline job time to 2 hours
>>
>> Hi Mike,
>>
>> Is the plan to keep it at a 2 hour limit indefinitely (not just for
>> these large series currently outstanding)?
>>
>> Thanks,
>> Michael
>>
>> On 11/23/2021 7:44 PM, Michael D Kinney wrote:
>>> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3750
>>>
>>> Large patches that modify a large number of files(e.g uncrustify)
>>> take longer to process through CI checks such as ECC. Increase
>>> the max job time from 1 hour to 2 hours to accommodate larger patch
>>> series.
>>>
>>> Cc: Sean Brogan <sean.brogan@microsoft.com>
>>> Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>
>>> Cc: Liming Gao <gaoliming@byosoft.com.cn>
>>> Cc: Michael Kubacki <michael.kubacki@microsoft.com>
>>> Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com>
>>> ---
>>> .azurepipelines/templates/pr-gate-build-job.yml | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/.azurepipelines/templates/pr-gate-build-job.yml b/.azurepipelines/templates/pr-gate-build-job.yml
>>> index d5b16c127f58..244cffdbfaba 100644
>>> --- a/.azurepipelines/templates/pr-gate-build-job.yml
>>> +++ b/.azurepipelines/templates/pr-gate-build-job.yml
>>> @@ -17,7 +17,7 @@ parameters:
>>> jobs:
>>>
>>> - job: Build_${{ parameters.tool_chain_tag }}
>>> -
>>> + timeoutInMinutes: 120
>>> #Use matrix to speed up the build process
>>> strategy:
>>> matrix:
>>>
next prev parent reply other threads:[~2021-11-24 2:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 0:44 [Patch 1/1] .azurepipelines/templates: Update max pipeline job time to 2 hours Michael D Kinney
2021-11-24 0:48 ` [edk2-devel] " Michael Kubacki
2021-11-24 0:54 ` Michael D Kinney
2021-11-24 2:01 ` Michael Kubacki [this message]
2021-11-24 2:02 ` Michael Kubacki
2021-11-26 15:51 ` Sean
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=fed59a8a-5710-0610-5acf-b4c4a92c73dd@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