-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Spurious 3 hour timeout on the "dist-x86_64-apple" job #58506
Comments
FWIW, everything gets slower - I suspect something running in parallel on the same hardware. @alexcrichton - Do you know how many dedicated Macs we have? If it's less than 5 that could explain this since presumably in that case we run on the same machine sometimes. Maybe something else in rust-lang org also has macOS builders and Travis runs that in parallel, too. |
Can we not raise this time limit so we don't have to restart things and waste time? |
@Mark-Simulacrum FWIW we have 10 I believe |
@pietroalbini -- might be good to reach out to Travis and see if there's anyway we can get visibility into which Mac each job is getting scheduled; I wonder if we're sometimes scheduling onto the same mac (instead of using 5 different ones)... |
Contacted Travis Support about this. |
Travis Support replied, and while this is not the definitive answer (they didn't take a deeper look at the issue yet) it might be possible that we're overcommitting our dedicated Mac Pros if we run at full capacity, since the |
Build time time variance has leveled off in the recent week since this change was deployed on Travis's side, @kennytm do you know if this has come up much in the past week or so? |
@alexcrichton Nope, all 3-hour timeouts I knew in the past week were caused by Docker rebuild. |
Haven't seen this in quite some time now, so closing. |
Symptom: The
dist-x86_64-apple
takes >3 hours to complete, causing it to fail.We have investigated the timeouts and did not find any causes yet, other than "rustc becomes too slow to compile" (23 minutes → 30 minutes).
Previous instances:
The text was updated successfully, but these errors were encountered: