Ryzen 3900X test failures
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
Testing rr on Ryzen 3900X (after running the ryzen workaround) and I get the following failures:
The following tests FAILED:
565 - setuid-no-syscallbuf (Failed)
1102 - checksum_sanity_noclone (Failed)
The following tests FAILED:
1153 - record_replay-no-syscallbuf (Failed)
2394 - record_replay-32 (Failed)
I can reproduce setuid-no-syscallbuf with ctest -R sometimes, I cannot reproduce the other failures.
I'm not sure if 3900X should be added to the list of supported Ryzen CPUs, are these known bits of flakiness?
cc @glandium
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 reproducing setuid-no-syscallbuf with ctest -R on a Ryzen 3900X after applying the Ryzen workaround, then compare it with checksum_sanity_noclone, record_replay-no-syscallbuf, and record_replay-32. Review the supported Ryzen CPU handling and test results; done means determining whether these failures are expected, flaky, or require a tracked fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- operating-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100