From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/4] Azure: Set the timeout for jobs to the maximum
Date: Sun, 20 Aug 2023 13:31:26 -0400 [thread overview]
Message-ID: <20230820173129.781985-1-trini@konsulko.com> (raw)
As per current Azure Pipelines documentation we qualify for 3600 minutes
per job, if specified, as the timeout. The default unspecified timeout
is 60 minutes. Rework things to specify 0 as the timeout (and so maximum
allowed) so that we don't have failures due to running slightly past 60
minutes total.
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>
---
.azure-pipelines.yml | 1 +
1 file changed, 1 insertion(+)
diff --git a/.azure-pipelines.yml b/.azure-pipelines.yml
index 61d4bf8c8e5f..fc3188a806f4 100644
--- a/.azure-pipelines.yml
+++ b/.azure-pipelines.yml
@@ -468,6 +468,7 @@ stages:
- stage: world_build
jobs:
- job: build_the_world
+ timeoutInMinutes: 0 # Use the maximum allowed
displayName: 'Build the World'
pool:
vmImage: $(ubuntu_vm)
--
2.34.1
next reply other threads:[~2023-08-20 17:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-20 17:31 Tom Rini [this message]
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
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=20230820173129.781985-1-trini@konsulko.com \
--to=trini@konsulko.com \
--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