Increase timeout on OneFuzz deployment pipeline#124152
Merged
Conversation
Contributor
|
Tagging subscribers to this area: @dotnet/area-meta |
Contributor
There was a problem hiding this comment.
Pull request overview
Adjusts the Azure Pipelines job timeout for the libraries fuzzing “deploy to OneFuzz” pipeline so the nightly deployment run has enough time to complete reliably, reducing timeouts in CI.
Changes:
- Increased the
windowsjobtimeoutInMinutesfrom 240 to 600 for the OneFuzz deployment pipeline.
Member
Author
|
/ba-g Internal pipeline-only change |
liveans
approved these changes
Feb 13, 2026
richlander
pushed a commit
to richlander/runtime
that referenced
this pull request
Feb 14, 2026
iremyux
pushed a commit
to iremyux/dotnet-runtime
that referenced
this pull request
Mar 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
It's constantly on the edge of or exceeding the current timeout