From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Cc: Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH 2/4] Azure: Rework build the world jobs
Date: Wed, 6 Sep 2023 21:52:41 -0400 [thread overview]
Message-ID: <20230907015241.GL305624@bill-the-cat> (raw)
In-Reply-To: <20230820173129.781985-2-trini@konsulko.com>
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
On Sun, Aug 20, 2023 at 01:31:27PM -0400, Tom Rini wrote:
> Now that we have 3600 minutes per build job, condense and rework things
> such that our overall time largely doesn't change, but we can also
> largely avoid having to re-tweak this job to avoid timeouts. Given that
> we have 10 threads, we also move a few of the specific sandbox test
> builds to a prior stage.
>
> Note that while sandbox builds with address sanitization enabled (ASAN)
> not all tests pass, so we limit ourselves to just checking that the
> version test passes for now.
>
> Link: https://learn.microsoft.com/en-us/azure/devops/pipelines/process/phases?view=azure-devops&tabs=yaml#timeouts
> Signed-off-by: Tom Rini <trini@konsulko.com>
> Reviewed-by: Simon Glass <sjg@chromium.org>
Applied to u-boot/next, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-09-07 1:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-20 17:31 [PATCH 1/4] Azure: Set the timeout for jobs to the maximum Tom Rini
2023-08-20 17:31 ` [PATCH 2/4] Azure: Rework build the world jobs Tom Rini
2023-08-21 19:11 ` Simon Glass
2023-09-07 1:52 ` Tom Rini [this message]
2023-08-20 17:31 ` [PATCH 3/4] CI: Combine tools-only and envtools jobs Tom Rini
2023-08-21 19:11 ` Simon Glass
2023-09-07 1:52 ` Tom Rini
2023-08-20 17:31 ` [PATCH 4/4] CI: Drop some jobs we didn't really utilize Tom Rini
2023-08-21 19:11 ` Simon Glass
2023-09-07 1:52 ` Tom Rini
2023-08-21 19:11 ` [PATCH 1/4] Azure: Set the timeout for jobs to the maximum Simon Glass
2023-08-29 14:09 ` Tom Rini
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-all 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=20230907015241.GL305624@bill-the-cat \
--to=trini@konsulko.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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