Meta tracking issue for spurious CI failures #133959
Labels
A-CI
Area: Our Github Actions CI
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
S-tracking-forever
Status: Never to be closed.
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
T-infra
Relevant to the infrastructure team, which will review and decide on the PR/issue.
This is a (meta) tracking issue intended to make it easier to find the specific spurious CI failure issues.
Platform-specific
tests\mir-opt\strip_debuginfo.rs
Cannot create a file when that file already exists.` #134351; CI-spurious-fail-msvcrustc
itself in x86_64 apple CI jobs #134220; CI-spurious-x86_64-apple-SIGSEGV-SIGILLRunner-specific
Known problems
LLVM
Pointer provenance ABA lockless queue test failures
Linkers
rust-lld
can sometimes crash quite oftenrust-lld
causes SIGSEGV in FFI code #128286Networking failures
Bot troubles
Possible mitigation approaches
cargo
invocations if stderr contains a known pattern #134472Others
npm ci
segfault: Rollup of 12 pull requests #136572 (comment), rustdoc: run css and html minifier at build instead of runtime #136253 (comment)The text was updated successfully, but these errors were encountered: