-
Notifications
You must be signed in to change notification settings - Fork 1
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
Intermittent failure on t/04-nativecall/13-union.t #5187
Comments
From @cokeTest Summary Report t/04-nativecall/13-union.t (Wstat: 65280 Tests: 26 Failed: 0) $ sw_vers -- |
From @FROGGSHi, can I get verbose output please? |
The RT System itself - Status changed from 'new' to 'open' |
From @coke$ prove -v -e ./perl6 t/04-nativecall/13-union.t # Looks like you planned 28 tests, but ran 26 Test Summary Report t/04-nativecall/13-union.t (Wstat: 65280 Tests: 26 Failed: 0) |
1 similar comment
From @coke$ prove -v -e ./perl6 t/04-nativecall/13-union.t # Looks like you planned 28 tests, but ran 26 Test Summary Report t/04-nativecall/13-union.t (Wstat: 65280 Tests: 26 Failed: 0) |
From @lizmat
This seems to have been fixed (aka, worked around) with 1bbef9894156d7d3267 . I suggest closing this ticket, and thus removing the blocker for 2016.03. Liz |
From @cokeOn Sun Mar 20 15:03:37 2016, elizabeth wrote:
It's still failing here for me. -- |
From @jnthnOn Sun Mar 20 16:56:04 2016, coke wrote:
Has anybody seen this recently? I suspect it was fixed by 6733e927ceb1aeff0 in MoarVM, which addressed a GC bug in CUnion that torture testing drove out. That was fixed back in April, and I don't recall seeing the test fail since then. |
From @lizmatFWIW, I haven’t seen it in months… and I basically run at least 10 spectests a day. Liz
|
From @jnthnOn Thu Jul 21 05:14:07 2016, elizabeth wrote:
Aye, but it's in "make test", not "make spectest". Do you run that so often too? :-) |
From @stmukI've run roast a handful of times in the last few days and didn't see S On 21 July 2016 at 12:03, jnthn@jnthn.net via RT
-- |
From @jnthnOn Wed Jul 27 17:43:50 2016, steve.mynott@gmail.com wrote:
Not heard anyone mention it in a while either, nor seen it myself. Since we have a good candidate for a commit that likely fixed the issue, I'll resolve this RT now. Can always re-open if it crops up again. |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#127750 (status was 'resolved')
Searchable as RT127750$
The text was updated successfully, but these errors were encountered: