From @coke

Test Summary Report

t/04-nativecall/13-union.t (Wstat​: 65280 Tests​: 26 Failed​: 0)
  Non-zero exit status​: 255
  Parse errors​: Bad plan. You planned 28 tests but ran 26.
Files=45, Tests=593, 23 wallclock secs ( 0.26 usr 0.14 sys + 71.66
cusr 6.59 csys = 78.65 CPU)
Result​: FAIL

$ sw_vers
ProductName​: Mac OS X
ProductVersion​: 10.10.5
BuildVersion​: 14F1605

--
Will "Coke" Coleda

From @FROGGS

Hi, 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
t/04-nativecall/13-union.t ..
1..28
ok 1 - sizeof union is sizeof biggest member
ok 2 - sizeof(MyStruct)
ok 3 - getting long
ok 4 - getting num
ok 5 - getting int8
ok 6 - getting num32
ok 7 - getting long from C-created struct
ok 8 - getting num from C-created struct
ok 9 - getting int8 from C-created struct
ok 10 - getting num32 from C-created struct
ok 11 - long in union
ok 12 - int in union
ok 13 - short in union
ok 14 - char in union
ok 15 - sizeof(MyStruct2)
ok 16 - getting long from C-created struct
ok 17 - getting num from C-created struct
ok 18 - getting int8 from C-created struct
ok 19 - getting num32 from C-created struct
ok 20 - long in union*
ok 21 - int in union*
ok 22 - short in union*
ok 23 - char in union*
ok 24 - sizeof(UnionOfStructs)
ok 25 - member a of union is-a MyStruct
ok 26 - member b of union is-a YourStruct
Cannot look up attributes in a type object
  in block <unit> at t/04-nativecall/13-union.t line 137

# Looks like you planned 28 tests, but ran 26
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 2/28 subtests

Test Summary Report

t/04-nativecall/13-union.t (Wstat​: 65280 Tests​: 26 Failed​: 0)
  Non-zero exit status​: 255
  Parse errors​: Bad plan. You planned 28 tests but ran 26.
Files=1, Tests=26, 1 wallclock secs ( 0.03 usr 0.01 sys + 1.52 cusr 0.09 csys = 1.65 CPU)
Result​: FAIL

From @lizmat

On 20 Mar 2016, at 19​:17, Will Coleda (via RT) <perl6-bugs-followup@​perl.org> wrote​:

# New Ticket Created by Will Coleda
# Please include the string​: [perl #​127750]
# in the subject line of all future correspondence about this issue.
# <URL​: https://rt-archive.perl.org/perl6/Ticket/Display.html?id=127750 >

Test Summary Report
-------------------
t/04-nativecall/13-union.t (Wstat​: 65280 Tests​: 26 Failed​: 0)
Non-zero exit status​: 255
Parse errors​: Bad plan. You planned 28 tests but ran 26.
Files=45, Tests=593, 23 wallclock secs ( 0.26 usr 0.14 sys + 71.66
cusr 6.59 csys = 78.65 CPU)
Result​: FAIL

$ sw_vers
ProductName​: Mac OS X
ProductVersion​: 10.10.5
BuildVersion​: 14F1605

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 @coke

On Sun Mar 20 15​:03​:37 2016, elizabeth wrote​:

On 20 Mar 2016, at 19​:17, Will Coleda (via RT) <perl6-bugs-
followup@​perl.org> wrote​:

# New Ticket Created by Will Coleda
# Please include the string​: [perl #​127750]
# in the subject line of all future correspondence about this issue.
# <URL​: https://rt-archive.perl.org/perl6/Ticket/Display.html?id=127750 >

Test Summary Report
-------------------
t/04-nativecall/13-union.t (Wstat​: 65280 Tests​: 26
Failed​: 0)
Non-zero exit status​: 255
Parse errors​: Bad plan. You planned 28 tests but ran 26.
Files=45, Tests=593, 23 wallclock secs ( 0.26 usr 0.14 sys + 71.66
cusr 6.59 csys = 78.65 CPU)
Result​: FAIL

$ sw_vers
ProductName​: Mac OS X
ProductVersion​: 10.10.5
BuildVersion​: 14F1605

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

It's still failing here for me.

--
Will "Coke" Coleda

From @jnthn

On Sun Mar 20 16​:56​:04 2016, coke wrote​:

On Sun Mar 20 15​:03​:37 2016, elizabeth wrote​:

On 20 Mar 2016, at 19​:17, Will Coleda (via RT) <perl6-bugs-
followup@​perl.org> wrote​:

# New Ticket Created by Will Coleda
# Please include the string​: [perl #​127750]
# in the subject line of all future correspondence about this issue.
# <URL​: https://rt-archive.perl.org/perl6/Ticket/Display.html?id=127750 >

Test Summary Report
-------------------
t/04-nativecall/13-union.t (Wstat​: 65280 Tests​: 26
Failed​: 0)
Non-zero exit status​: 255
Parse errors​: Bad plan. You planned 28 tests but ran 26.
Files=45, Tests=593, 23 wallclock secs ( 0.26 usr 0.14 sys + 71.66
cusr 6.59 csys = 78.65 CPU)
Result​: FAIL

$ sw_vers
ProductName​: Mac OS X
ProductVersion​: 10.10.5
BuildVersion​: 14F1605

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

It's still failing here for me.

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 @lizmat

FWIW, I haven’t seen it in months… and I basically run at least 10 spectests a day.

Liz

On 21 Jul 2016, at 13​:18, Steve Mynott <steve.mynott@​gmail.com> wrote​:

I've run roast a handful of times in the last few days and didn't see
that fail once.

S

On 21 July 2016 at 12​:03, jnthn@​jnthn.net via RT
<perl6-bugs-followup@​perl.org> wrote​:

On Sun Mar 20 16​:56​:04 2016, coke wrote​:

On Sun Mar 20 15​:03​:37 2016, elizabeth wrote​:

On 20 Mar 2016, at 19​:17, Will Coleda (via RT) <perl6-bugs-
followup@​perl.org> wrote​:

# New Ticket Created by Will Coleda
# Please include the string​: [perl #​127750]
# in the subject line of all future correspondence about this issue.
# <URL​: https://rt-archive.perl.org/perl6/Ticket/Display.html?id=127750 >

Test Summary Report
-------------------
t/04-nativecall/13-union.t (Wstat​: 65280 Tests​: 26
Failed​: 0)
Non-zero exit status​: 255
Parse errors​: Bad plan. You planned 28 tests but ran 26.
Files=45, Tests=593, 23 wallclock secs ( 0.26 usr 0.14 sys + 71.66
cusr 6.59 csys = 78.65 CPU)
Result​: FAIL

$ sw_vers
ProductName​: Mac OS X
ProductVersion​: 10.10.5
BuildVersion​: 14F1605

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

It's still failing here for me.

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.

--
4096R/EA75174B Steve Mynott <steve.mynott@​gmail.com>

From @jnthn

On Thu Jul 21 05​:14​:07 2016, elizabeth wrote​:

FWIW, I haven’t seen it in months… and I basically run at least 10
spectests a day.

Aye, but it's in "make test", not "make spectest". Do you run that so often too? :-)

From @stmuk

I've run roast a handful of times in the last few days and didn't see
that fail once.

S

On 21 July 2016 at 12​:03, jnthn@​jnthn.net via RT
<perl6-bugs-followup@​perl.org> wrote​:

On Sun Mar 20 16​:56​:04 2016, coke wrote​:

On Sun Mar 20 15​:03​:37 2016, elizabeth wrote​:

On 20 Mar 2016, at 19​:17, Will Coleda (via RT) <perl6-bugs-
followup@​perl.org> wrote​:

# New Ticket Created by Will Coleda
# Please include the string​: [perl #​127750]
# in the subject line of all future correspondence about this issue.
# <URL​: https://rt-archive.perl.org/perl6/Ticket/Display.html?id=127750 >

Test Summary Report
-------------------
t/04-nativecall/13-union.t (Wstat​: 65280 Tests​: 26
Failed​: 0)
Non-zero exit status​: 255
Parse errors​: Bad plan. You planned 28 tests but ran 26.
Files=45, Tests=593, 23 wallclock secs ( 0.26 usr 0.14 sys + 71.66
cusr 6.59 csys = 78.65 CPU)
Result​: FAIL

$ sw_vers
ProductName​: Mac OS X
ProductVersion​: 10.10.5
BuildVersion​: 14F1605

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

It's still failing here for me.

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.

--
4096R/EA75174B Steve Mynott <steve.mynott@​gmail.com>

From @jnthn

On Wed Jul 27 17​:43​:50 2016, steve.mynott@​gmail.com wrote​:

I've run roast a handful of times in the last few days and didn't see
that fail once.

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'