Skip to content

Spurious failures in sccache #40240

New issue
New issue
Closed
#41623
Closed
Spurious failures in sccache#40240
#41623

Description

@alexcrichton

alexcrichton
openedon Mar 3, 2017

Outstandling failures:

Failed to spawn child broken pipe

maybe fixed in #40809?

error: failed to execute compile
caused by: failed to spawn child
caused by: Broken pipe (os error 32)
make[3]: *** [bin/llvm-config] Error 2

Notes:

Error 254

Suspected bug in sccache. Hidden by mozilla/sccache#82 by accident. Sccache update in #40676

maybe fixed in #40809?

notes:

  • One job failed nul bytes in env, args, or program passed to Command when creating preprocessor. This seems crazy. Memory corruption?
  • OSX or Linux so far, no Windows.
  • Most indicate just one compilation failing, the last log indicates the entire server crashed w/ a segfault or something

Fixed failures

Unexpected EOF

Hoping to be fixed by mozilla/sccache#79

error: failed to execute compile
caused by: error reading compile response from server
caused by: IoError(Error { repr: Custom(Custom { kind: Other, error: StringError("unexpected EOF") }) })
caused by: unexpected EOF
make[3]: *** [tools/llvm-readobj/CMakeFiles/llvm-readobj.dir/ELFDumper.cpp.o] Error 2

Forcibly closed by remote host

Suspected fixed in mozilla/sccache@5f6932b

PR sent in #40676

error: failed to execute compile
caused by: Failed to send data to or receive data from server
caused by: IoError(Error { reprError { : Os { code: 10054repr: Os { code: 10054, message: "An existing connection was forcibly closed by the remote host." } })

notes:

  • Only windows so far
  • Both 32 and 64 bit
  • Ignore segfaults, they're likely Remove dependency on named_pipe mozilla/sccache#83
  • Both beginning and end of the build
  • appears that the server process is crashing
  • suspect, crossbeam segfaulting (there are known segfaults in there)

Wedged 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    A-spuriousArea: Spurious failures in builds (spuriously == for no apparent reason)Area: Spurious failures in builds (spuriously == for no apparent reason)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions