-
Notifications
You must be signed in to change notification settings - Fork 26.3k
[CD] Increase timeout for windows binary builds #147390
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/147390
Note: Links to docs will display an error until the docs builds have been completed. ❌ 4 New Failures, 26 PendingAs of commit f1a93e4 with merge base 57060be ( NEW FAILURES - The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
malfet
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please include before/after stats (and perhaps PR that introduces timeout. 240 min is already ridiculously long)
|
Looks like up to Jan 31, 3h 37m - 3h 50m And Jan 31 we started seeing timeouts: The build time increased to 3h 55m + |
|
cc @clee2000 as you might be interested in this increase |
|
We are seeing increase in cuda jobs could this be related to CUDA PRs ? Could this issue be related to: |
|
@pytorchmergebot merge -f "lint is green failures are not related" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Mitigates #147376