-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Failed stability upload causes remainder of build to not execute #19079
Comments
This is actually failing the build completely because the step ends with an exception not a failure. @sa2ajj suggested overriding |
Just setting max_builds=1 for the windows slaves might also fix this. |
First I might try putting a lock around this step, assuming there is a bug in the DirectoryUpload buildstep. |
Putting a lock around DirectoryUpload did nothing. |
Here's a dump of the log
|
@brson did you try to run only one instance? (I need a Windows instance to check the things myself, but it will only happen on Monday.) |
@sa2ajj We made it through yesterday with one build per slave and none of these failures. Seems like a good sign. |
Yes, it is a good sign :) But that makes me wonder why the same temporary file can somehow be used by different processes... |
Buildbots no longer try to upload these metrics so this is moot. |
See http://buildbot.rust-lang.org/builders/auto-win-64-opt/builds/817.
Stability upload is set to
haltOnFailure=False
which should allow it to fail, while continuing to execute the remaining build steps, but what actually happens is that the overall build succeeds but none of the subsequent steps execute.The text was updated successfully, but these errors were encountered: