Skip to content

Tracking issue for Spurious failure in sccache: "Invalid checksum" #43775

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.

Sign up for GitHub

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

Jump to bottom
Closed
kennytm opened this issue Aug 9, 2017 · 1 comment
Closed

Tracking issue for Spurious failure in sccache: "Invalid checksum" #43775

kennytm opened this issue Aug 9, 2017 · 1 comment
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.

Comments

@kennytm
Copy link
Member

kennytm commented Aug 9, 2017

Seen on #43652 and #43732, happens during LLVM compilation. Error log will contain something like:

ERROR:sccache::server: ["ARMFastISel.cpp.o"] fatal error: Error(Io(Error { repr: Custom(Custom { kind: Other, error: StringError("Invalid checksum") }) }), State { next_error: None })

cc mozilla/sccache#171.
@kennytm kennytm mentioned this issue Aug 9, 2017
Closed
@aturon aturon added the A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) label Aug 9, 2017
@Mark-Simulacrum Mark-Simulacrum added the C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC label Aug 10, 2017
@jonas-schievink jonas-schievink added the T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. label Nov 26, 2019
@Mark-Simulacrum
Copy link
Member

I think we've not seen this recently, so going to go ahead and close. We also recently upgraded sccache to a somewhat newer version on macOS and Linux, which may have further helped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kennytm @aturon @jonas-schievink @Mark-Simulacrum