-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Attempt to debug 259 exit code on AppVeyor #57975
Conversation
Let's try to dig in a bit more and see where this is coming from, it looks like AppVeyor is also unsure where this is coming from!
(rust_highfive has picked a reviewer for you, use r? to override) |
This came out with some discussion I've been having with them. |
@bors r+ |
📌 Commit ce279a8 has been approved by |
NB: you can RDP directly into an appveyor machine, so perhaps setting that up would help? |
Unfortunately we don't typically get a chance to see and debug these failures until hours after the build has finished. Additionally they're often spurious, and we can't be watching every single build. |
@bors p=1 Adjusting queue order relative to rollup. |
Attempt to debug 259 exit code on AppVeyor Let's try to dig in a bit more and see where this is coming from, it looks like AppVeyor is also unsure where this is coming from!
☀️ Test successful - checks-travis, status-appveyor |
☀️ Test successful - checks-travis, status-appveyor |
Still happening, opened a tracking issue in #58160. |
Let's try to dig in a bit more and see where this is coming from, it
looks like AppVeyor is also unsure where this is coming from!