-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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 failures in sccache #40240
Comments
I've made a PR to sccache to hopefully squash at least some of the spurious failures we've been seeing (I don't think it will fix all of them though) |
The first failure above is getting an EPIPE on this line which baffles me. I have no idea how an EPIPE would arise during process creation. |
Looking at the two lines above, there's |
I've built a local copy with mozilla/sccache#79 and mozilla/sccache#78. Let's see if that helps rust-lang#40240!
Looks like "broken pipe" errors are indeed coming from kevent, confirmed now that I've tested on an older mac. tokio-rs/mio#583 should fix. |
I've tracked down what I believe is the last spurious sccache failure on rust-lang#40240 to behavior in mio (tokio-rs/mio#583), and this commit updates the binaries to a version which has that fix incorporated.
I've tracked down what I believe is the last spurious sccache failure on rust-lang#40240 to behavior in mio (tokio-rs/mio#583), and this commit updates the binaries to a version which has that fix incorporated.
…sxcv travis: Update sccache binaries I've tracked down what I believe is the last spurious sccache failure on rust-lang#40240 to behavior in mio (tokio-rs/mio#583), and this commit updates the binaries to a version which has that fix incorporated.
…sxcv travis: Update sccache binaries I've tracked down what I believe is the last spurious sccache failure on rust-lang#40240 to behavior in mio (tokio-rs/mio#583), and this commit updates the binaries to a version which has that fix incorporated.
Haven't seen any new issues in the past week or so, so assuming that we can close this now. Yay! |
Again a broken pipe spawn :(
|
Oh oops, the fix in mio wasn't actually released until mio 0.6.7 came out on crates.io. I was using a local override previously but when I recently rebuilt sccache I used the crates.io version and forgot that. To fix that we need to update sccache's Cargo.lock to pull in an updated mio, make new binaries, upload them, and then make a PR. @TimNN you scared me, my weekend was almost ruined! :) |
Contains tokio-rs/mio#583 to fix tokio-rs/mio#582, transitively fixing flakiness discovered in rust-lang/rust#40240.
I've updated sccache's mio, next step is binaries. I'll be flying for the next ~20 hours and won't have the ability to do so until I land unfortunately :( |
oops didn't mean to close |
Pulls in mozilla/sccache@ef0d77543 to fix rust-lang#40240 again after the builds included in rust-lang#41447 forgot to include the mio fixed included in rust-lang#41076. Closes rust-lang#40240
ci: Update sccache build Pulls in mozilla/sccache@ef0d77543 to fix #40240 again after the builds included in #41447 forgot to include the mio fixed included in #41076. Closes #40240
There has been two sccache failure this week, both talking about invalid checksum. 43652 (failure on Linux):
43732 (failure on Windows):
Reopen? |
I think this issue is probably no longer useful, @kennytm mind opening a new issue? You can cc mozilla/sccache#171, the upstream report tracking this. |
@alexcrichton Opened #43775. |
Thanks! |
Outstandling failures:
Failed to spawn child broken pipe
maybe fixed in #40809?Notes:
no theoriesmaybe suspicion: EPIPE coming out ofregister
on OSX tokio-rs/mio#582?Error 254
Suspected bug in sccache. Hidden by mozilla/sccache#82 by accident. Sccache update in #40676
maybe fixed in #40809?
notes:
Command
when creating preprocessor. This seems crazy. Memory corruption?Fixed failures
Unexpected EOF
Hoping to be fixed by mozilla/sccache#79
Forcibly closed by remote host
Suspected fixed in mozilla/sccache@5f6932b
PR sent in #40676
notes:
named_pipe
mozilla/sccache#83Wedged in build logs
wedged in mio, likely fixed in #40809
Errors not at the fault of sccache
ar.exe/ranlib errors
More tracked at #40546 suspected to be unrelated to sccache and instead related to MinGW makefiles (and how they're not always the best...)
Hoping to be fixed by #40548
The text was updated successfully, but these errors were encountered: