[test] xfail concurrency tests under valgrind on Linux ARM - #19
Merged
Conversation
Test Results
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There is an issue seen on Valgrind ARM: "unrecognised instruction at 0x35b8702c" on the nightlies.
The LDAPRB instruction (ARMv8.3 FEAT_LRCPC load-acquire byte) is an atomic acquire load. The JIT emits it because the arm runner's CPU supports LRCPC, but valgrind 3.22.0 can't decode it, so valgrind raises SIGILL and kills pytest mid-suite. Memcheck itself reports 0 errors.
This is valgrind bug 476465, fixed in valgrind 3.26.0 (https://sourceware.org/git/?p=valgrind.git;a=commit;h=41e2f95cf129191555e0048ccbbb392ee0fb155e) but that release is not available on ubuntu24
This PR hence marks the test xfail under valgrind until a newer distro ships the fix.