Investigate why repr-128-dwarf doesn't fail in CI test jobs
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
I'm not sure why this passes in CI though.
Surely we have some jobs that enable LLVM assertions?Seems like not, test jobs typically don't enable LLVM assertions due to slowness.That doesn't sound right. LLVM assertions are supposed to be enabled for all test jobs, except those marked NO_LLVM_ASSERTIONS, which is only the apple ones.
Originally posted by @nikic in #138254
Contributor 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 examining the CI test jobs and how LLVM assertions are enabled or disabled, especially the NO_LLVM_ASSERTIONS exception for Apple jobs. Reproduce the repr-128-dwarf behavior in the relevant CI configuration and determine why the expected failure is not occurring. Done means the cause is identified and the affected test jobs behave as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, compilers, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100