Meta tracking issue for spurious CI failures

[jieyouxu]

This is a (meta) tracking issue intended to make it easier to find the specific spurious CI failure issues.

Platform-specific

• Tracking Issue for high failure rates on Windows MSVC CI with filesystem errors #127883; CI-spurious-fail-msvc CI spurious failure: target env msvc
• Tracking Issue for spurious mingw CI failures #133958; CI-spurious-fail-mingw CI spurious failure: target env mingw
• SIGSEGV/SIGILL while building rustc itself in x86_64 apple CI jobs #134220; CI-spurious-x86_64-apple-SIGSEGV-SIGILL CI spurious failure: SIGSEGV/SIGILL while building rustc itself on x86_64-apple

Runner-specific

• Sporadic errors with armhf-gnu CI remote test runs #97669

Known problems

LLVM

• llvm-tblgen Segmentation fault in CI on dist-aarch64-apple #109624
• random Empty/Tombstone LLVM assertion error on i686-msvc CI #110290

Pointer provenance ABA lockless queue test failures

• ABA pointer provenance lockless queue test failures due to ABA-problem with pointer provenance in lockless queues #121950, CI-ABA-ptr-provenance-lockless-queue-fail CI spurious failure: related to #121950

Linkers

rust-lld can sometimes crash quite often

• Linking with rust-lld causes SIGSEGV in FFI code #128286

Networking failures

• Tracking issue for spurious network failures on bots #40474

Bot troubles

• Bors: 422 Update is not a fast forward #43535

[matthiaskrgr]

https://github.com/rust-lang/rust/issues?q=is%3Aissue%20state%3Aopen%20label%3AA-spurious