New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Floppage of atomic tests #6492
Comments
From @AlexDanielHere's the output when it fails: ok 1 - Can do an atomic fetch from a Scalar container # Looks like you planned 28 tests, but ran 10 I noticed that it fails more often when the system is under load (e.g. when running the spectest). Other than that I don't have any info. |
From @AlexDanielOh. A crude way to reproduce it is: while :; do clear; PERL6LIB=lib ./perl6-m t/spec/S17-lowlevel/atomic-ops.t || break; done And just leave it running, it'll fail at some point. Get your system busy with something and it'll fail faster. On 2017-09-05 00:14:11, alex.jakimenko@gmail.com wrote:
|
From @ninerA golfed version that reliably fails: { The important bit is the Int being read atomicly before reading the atomicint. The sleep makes it fail reliably. |
From @jnthnOn Tue, 05 Sep 2017 00:36:34 -0700, nine@detonation.org wrote:
And that in turn got it down to being a spesh bug (this golf reliably worked with MVM_SPESH_DISABLE=1), which was that it mis-optimized the call to the wrong multi candidate, due to some bogus logging. Fixed with MoarVM/MoarVM@5bf652e (though the spesh output it isn't too great, so I'll now see if I can do some further tweaks to get it inlining the prefix:<⚛> for atomicint). /jnthn |
The RT System itself - Status changed from 'new' to 'open' |
@jnthn - Status changed from 'open' to 'resolved' |
From @lizmatFWIW, I couldn’t get this to fail on my MBP *while* running make spectest with TEST_JOBS=8 Perhaps this is OS / CPU / compiler dependent?
|
Migrated from rt.perl.org#132029 (status was 'resolved')
Searchable as RT132029$
The text was updated successfully, but these errors were encountered: