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
Bad plan: t/spec/S29-conversions/ord_and_chr.rakudo #407
Comments
From @Ovidt/spec/S29-conversions/ord_and_chr.rakudo fails with: t/spec/S29-conversions/ord_and_chr.rakudo (Wstat: 10 Tests: 170 Failed: 0) However, it runs to completion with: ./perl6 t/spec/S29-conversions/ord_and_chr.rakudo fails with: The problem is that, when running it as a test, it appears to hang between these two for loops, and then exits: for @maps -> $char, $code { for 0..31 -> $code { In testing, I put "say 1" between the two loops and the test ran to completion. Cheers, |
From @pmichaudOn Wed, Nov 12, 2008 at 03:35:08PM -0800, curtis_ovid_poe@yahoo.com (via RT) wrote:
This appears to be one of our heisenbugs -- it occurs in some For example in r32625 I get a similar situation with In contrast, for r32625 I don't see the ord_and_chr.t failure you In the assign.t case, it appears this may be related to the fact that # works # fails Again, this is all with r32625, YMMV with other revisions (and please Thanks! Pm |
The RT System itself - Status changed from 'new' to 'open' |
From publiustemp-perl6compiler2@yahoo.com--- On Thu, 13/11/08, Patrick R. Michaud <pmichaud@pobox.com> wrote:
Ah, sorry. I should have known better :) r32580 $ uname -a Now this test passes (r32629), but the Perl 6 test suite is still failing. Now, however, I can't tell which test fails. The output was confusing enough to me that I've copied it to a file and attached it (teeing the spectest rusults to a file was spectacularly disappointing. It doesn't play well with tee). Cheers, |
From publiustemp-perl6compiler2@yahoo.comperl6 $ make spectest Test Summary Report Files=220, Tests=6487, 304 wallclock secs ( 1.65 usr 0.82 sys + 539.47 cusr 22.60 csys = 564.54 CPU) |
From @markjreedOn Thu, Nov 13, 2008 at 5:31 PM, Ovid
Seems like the summary report should at least include counts of passed vs Test Summary Report Files=220, Tests=6487, 304 wallclock secs ( 1.65 usr 0.82 sys + It would also help if the actual test output weren't overrun with "Use of -- |
From @markjreedI retract the previous comment. It was based on the file sent by Ovid; when Failed Test Stat Wstat Total Fail List of Failed t/spec/S12-class/declaration-order.t 0 6 2 0 ?? Failed 1/219 test scripts. 0/6484 subtests failed. On Thu, Nov 13, 2008 at 6:03 PM, Mark J. Reed <markjreed@gmail.com> wrote:
-- |
From @pmichaudOn Thu, Nov 13, 2008 at 06:03:09PM -0500, Mark J. Reed wrote:
In some cases it's bad tests -- i.e., tests that are using In other cases it's failing tests -- the test fails in a way We could potentially see about disabling the warnings, but Pm |
From @pmichaudOn Thu, Nov 13, 2008 at 06:03:09PM -0500, Mark J. Reed wrote:
IIUC, the harness that rakudo is using is ultimately passing control Since Test::Harness didn't really output the statistics I was [*] At this stage of development, I'm more interested in how Pm |
From publiustemp-perl6compiler2@yahoo.com--- On Thu, 13/11/08, Mark J. Reed <markjreed@gmail.com> wrote:
Aha! Mark, what version of Test::Harness are you running? This looks like 2.X version output and I'm running 3.15. There might be a bug in the newer version which is losing that information. My best friend from the US arrives in a few hours, though, so there's not likely to be much follow up from me. Sorry. Cheers, |
From @pmichaudIs t/spec/S29-conversions/ord_and_char.t still failing for anyone? If Pm |
From @moritzPatrick R. Michaud via RT wrote:
It's fine here. Cheers, |
From jswitzer@gmail.comOn Mon Dec 15 17:03:51 2008, moritz wrote:
As of index 78b38ad..61c292d and r25170, I'm not able to reproduce this -Jason "s1n" Switzer |
@moritz - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#60510 (status was 'resolved')
Searchable as RT60510$
The text was updated successfully, but these errors were encountered: