Repository navigation
chore: Increase timeout seconds of R2R test - #3297
Merged
timcassell merged 1 commit intoOct 17, 2026
Merged
Conversation
timcassell
approved these changes
Oct 17, 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
2 participants
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.
This PR increase R2RTests timeout value from 360s to 540s.
Currently R2RTests
dotnet publishcommand takes about 175 seconds on succeeded.But there is cases, it take times and exceed build timeout on
macos(x64)CI Logs
https://github.com/dotnet/BenchmarkDotNet/actions/runs/38976004672
It looks like normal execution time seems not changed from previous PR(#3085).
Though, in some conditions, it takes over 360 seconds. or cause deadlock or freeze?