use 100 minute timeout for azure mingw32 job#5646
Merged
martin-frbg merged 1 commit intoOpenMathLib:developfrom Feb 12, 2026
Merged
use 100 minute timeout for azure mingw32 job#5646martin-frbg merged 1 commit intoOpenMathLib:developfrom
martin-frbg merged 1 commit intoOpenMathLib:developfrom
Conversation
Contributor
Author
|
CI is passing, including azure. Looking at the logs, this is the first green CI run on azure since Dec 25. Edit: the Dec 25 run was 58 minutes, the current run is 1hr4min. 100 minutes seems safe. |
Collaborator
|
Thanks - still annoying that it takes so long, but IIRC that's just mingw's way of handling files |
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.
The Windows_mingw_gmake job is consistently timing out at the default 60 minutes. Add an explicit timeout and make it 100 minutes.