Repository navigation
Raise the build job timeout to 120 minutes - #775
Merged
Merged
Conversation
The release build was cancelled at 60.6 minutes by the Azure Pipelines default: 'The job running on agent ... ran longer than the maximum time of 60 minutes.' NativeAOT for two architectures plus the test run no longer fits. CI builds the same thing, so it gets the same limit.
Copilot started reviewing on behalf of
Alexandre Zollinger Chohfi (azchohfi)
August 19, 2026 21:26
View session
Alexandre Zollinger Chohfi (azchohfi)
added a commit
that referenced
this pull request
Aug 19, 2026
The 0.6.2 release build was cancelled by Azure Pipelines at 60.6 minutes: ``` job 'Build' result=canceled duration=60.6 min error: The job running on agent Azure-Pipelines-1ESPT-ExDShared 65 ran longer than the maximum time of 60 minutes. ``` Neither pipeline set `timeoutInMinutes`, so both inherited the 60 minute default. NativeAOT for two architectures plus the test run no longer fits inside it, and the release stages that follow were all skipped as a result - nothing was published. Raises the `Build` job to 120 minutes in both `release.yml` and `ci.yml`. CI builds the same thing, so it is on the same trajectory even though it has not tripped yet. `fuzz.yml` already used 120, so this matches the existing precedent in the repo. This only changes the ceiling, not the build itself - a hung job now burns up to 120 minutes of agent time instead of 60. Worth a separate look at *why* the build takes this long, but that should not block the release.
Contributor
There was a problem hiding this comment.
Pull request overview
Raises CI and release build timeouts to accommodate NativeAOT builds and tests.
Changes:
- Sets both Build jobs to a 120-minute timeout.
- Matches the existing fuzz pipeline precedent.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
.pipelines/release.yml |
Raises release Build timeout to 120 minutes. |
.pipelines/ci.yml |
Raises CI Build timeout to 120 minutes. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This was referenced Sep 24, 2026
This was referenced Oct 2, 2026
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.
The 0.6.2 release build was cancelled by Azure Pipelines at 60.6 minutes:
Neither pipeline set
timeoutInMinutes, so both inherited the 60 minute default. NativeAOT for two architectures plus the test run no longer fits inside it, and the release stages that follow were all skipped as a result - nothing was published.Raises the
Buildjob to 120 minutes in bothrelease.ymlandci.yml. CI builds the same thing, so it is on the same trajectory even though it has not tripped yet.fuzz.ymlalready used 120, so this matches the existing precedent in the repo.This only changes the ceiling, not the build itself - a hung job now burns up to 120 minutes of agent time instead of 60. Worth a separate look at why the build takes this long, but that should not block the release.