Increase default timeout to 75 minutes for windows_arm64 build#129553
Open
Copilot wants to merge 2 commits into
Open
Increase default timeout to 75 minutes for windows_arm64 build#129553Copilot wants to merge 2 commits into
Copilot wants to merge 2 commits into
Conversation
….yml Co-authored-by: JulieLeeMSFT <63486087+JulieLeeMSFT@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Increase job timeout for windows_arm64 pipelines
platform-matrix: add default timeoutInMinutes: 75 for windows_arm64
Jun 18, 2026
JulieLeeMSFT
approved these changes
Jun 18, 2026
Contributor
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
Member
|
windows arm64 builds for ~10 pipelines have been timing out since end of May. Probably the build time increase from < 50min to > 50 min started when we started to build wasm. Increasing the timeout to 75min. |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR attempts to raise the default Azure Pipelines job timeout for the windows_arm64 platform fan-out in eng/pipelines/common/platform-matrix.yml (to reduce windows_arm64 job timeouts across multiple pipelines).
Changes:
- Adds a conditional default
timeoutInMinutes: 75injection in thewindows_arm64jobParametersblock when the caller has not supplied a timeout.
Comment on lines
+952
to
956
| # windows_arm64 agents are slower; give a larger default timeout, | ||
| # but only when the calling pipeline hasn't specified its own. | ||
| ${{ if eq(parameters.jobParameters.timeoutInMinutes, '') }}: | ||
| timeoutInMinutes: 75 | ||
| ${{ insert }}: ${{ parameters.jobParameters }} |
This was referenced Jun 18, 2026
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
windows_arm64 agents are slower than other platforms, causing stress/diagnostic pipeline jobs (jitstress, gcstress, superpmi, pgo, ilasm, etc.) to hit the default 60-minute ADO job timeout and Build fails.
All windows_arm64 jobs fan out through a single block in
eng/pipelines/common/platform-matrix.yml, so one targeted change covers all affected pipelines.Change
In the
windows_arm64block ofplatform-matrix.yml, injecttimeoutInMinutes: 75as a default — but only when the caller hasn't already supplied its own value:The guard
eq(parameters.jobParameters.timeoutInMinutes, '')is used instead ofcontainsValue(which inspects values, not keys). When a caller likelibraries-jitstress*.ymlalready passestimeoutInMinutes: 360, the guard is false and the default is suppressed — no duplicate-key error, and the existing 360 is preserved via${{ insert }}.All other platform blocks (windows_x64, windows_x86, linux_, osx_) are untouched.