increase Windows CI timeout again #2546
Merged
Conversation
This file contains 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
because the latest LLVM bump in PR onnx#2545 exceeded the 4.5h timeout see PR onnx#2511 for more context Signed-off-by: Soren Lassen <[email protected]>
jcwchen
approved these changes
Oct 4, 2023
|
Jenkins Linux amd64 Build #12910 [push] increase Windows CI time... started at 13:00 |
|
Jenkins Linux ppc64le Build #11927 [push] increase Windows CI time... started at 14:08 |
|
Jenkins Linux s390x Build #12934 [push] increase Windows CI time... started at 14:00 |
|
Jenkins Linux amd64 Build #12910 [push] increase Windows CI time... passed after 1 hr 10 min |
|
Jenkins Linux s390x Build #12934 [push] increase Windows CI time... passed after 1 hr 45 min |
|
Jenkins Linux ppc64le Build #11927 [push] increase Windows CI time... passed after 1 hr 52 min |
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.
because the latest LLVM bump in PR #2545 exceeded the 4.5h timeout
see PR #2511 for more context