rust-lang / rust-lang/rustc_codegen_gcc
Fix the tests of the crate portable-atomic
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 105
- Avg merge
- 8h 20m
- Merged PRs (30d)
- 14
Description
There are some failures on x86-64:
- test imp::atomic128::x86_64::tests::test_atomic_u128::compare_exchange ... FAILED
- test imp::atomic128::x86_64::tests::test_atomic_u128::compare_exchange_weak ... FAILED
- test imp::atomic128::x86_64::tests::test_atomic_u128::load_store ... SIGSEGV
and even more failures on m68k.
- Run the test of this crate in the CI?
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 running the named portable-atomic tests for x86-64 and reviewing the additional m68k failures. Then inspect how this crate is tested in the repository's CI configuration. Done means the reported failures and SIGSEGV are resolved and the crate's tests run in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100