Meta tracking issue for spurious CI failures

Open

#133,959 opened on Dec 6, 2024 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-CI A-spurious C-tracking-issue CI-ABA-ptr-provenance-lockless-queue-fail CI-spurious-fail-mingw CI-spurious-fail-msvc CI-spurious-fail-rust-lld-crash CI-spurious-x86_64-apple-SIGSEGV-SIGILL S-tracking-forever T-bootstrap T-compiler T-infra

Dominant language: Rust
Stars: 119k
Forks: 16.1k
PR merge metrics: PR metrics pending

Description

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

Platform-specific

Runner-specific

https://github.com/rust-lang/rust/issues/97669
(Unclear, under investigation) new arm64 runners behave strangely https://github.com/rust-lang/rust/issues/135867

Known problems

LLVM

Pointer provenance ABA lockless queue test failures

ABA pointer provenance lockless queue test failures due to #121950 in the miri test suite, https://github.com/rust-lang/rust/labels/CI-ABA-ptr-provenance-lockless-queue-fail

Linkers

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Research direction

Start by reviewing the linked platform-, runner-, LLVM-, linker-, networking-, and bot-related issues, along with the A-spurious label and listed mitigation approaches. The issue is a tracking index rather than a scoped change; done would require a clearly defined CI failure to investigate or a specific update to the referenced issue list.

Written by the indexing model from the issue text.

Assessment

Tech stack: rust
Domain: ci-cd
Issue type: Bug
Difficulty: 5/5
Estimated time: Over a week
Activity status: Stale
Clarity: Needs clarification
Newbie friendliness: 20/100

Meta tracking issue for spurious CI failures

Description

Platform-specific

Runner-specific

Known problems

LLVM

Pointer provenance ABA lockless queue test failures

Linkers

rust-lld can sometimes crash quite often

rust-lld fails with 0xc0000374 (STATUS_HEAP_CORRUPTION)

Networking failures

Bot troubles

Possible mitigation approaches

Others

Contributor guide

First steps

Research direction

Assessment

Get new issues in your inbox

`rust-lld` can sometimes crash quite often

`rust-lld` fails with `0xc0000374` (`STATUS_HEAP_CORRUPTION`)