Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[perl #32036] [BUG] t/pmc/signal.t fails

2 views
Skip to first unread message

Will Coleda

unread,
Oct 18, 2004, 7:32:18 PM10/18/04
to bugs-bi...@rt.perl.org
# New Ticket Created by Will Coleda
# Please include the string: [perl #32036]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=32036 >


I have a little smoke script I threw together that does a cvs checkout, config, make, make test:

Failed Test Stat Wstat Total Fail Failed List of Failed
-------------------------------------------------------------------------------
t/pmc/signal.t 1 256 3 1 33.33% 1
4 tests and 52 subtests skipped.
Failed 1/122 test scripts, 99.18% okay. 1/1943 subtests failed, 99.95% okay.

oolong:~ coke$ uname -a
Darwin oolong 7.5.0 Darwin Kernel Version 7.5.0: Thu Aug 5 19:26:16 PDT 2004; root:xnu/xnu-517.7.21.obj~3/RELEASE_PPC Power Macintosh powerpc
oolong:~ coke$ perl -v

This is perl, v5.8.1-RC3 built for darwin-thread-multi-2level
(with 1 registered patch, see perl -V for more detail)
<SNIP>

Seems to work fine with:
oolong:~/research/parrot_24673 coke$ perl t/harness t/pmc/signal.t
t/pmc/signal....ok
1/3 skipped: works standalone but not in test
All tests successful, 1 subtest skipped.
Files=1, Tests=3, 3 wallclock secs ( 1.18 cusr + 0.27 csys = 1.45 CPU)

My machine did happen to be under a bit of a load at the time the test ran, but that doesn't seem like much of an excuse. =) Going back through the output of the original harness, I get:

t/pmc/signal...................Hangup
oolong:~ coke$ # Failed test (t/pmc/signal.t at line 87)
# got: 'start
# never
# '
# expected: 'start
# '
t/pmc/signal...................NOK 1# Looks like you failed 1 tests of 3.
t/pmc/signal...................dubious
Test returned status 1 (wstat 256, 0x100)
DIED. FAILED test 1

Regards.

Leopold Toetsch

unread,
Oct 19, 2004, 3:42:39 AM10/19/04
to perl6-i...@perl.org
Will Coleda <parrotbug...@parrotcode.org> wrote:

> My machine did happen to be under a bit of a load at the time the test
> ran, but that doesn't seem like much of an excuse. =)

The test awaits the signal do be delivered in a second or so. Under load
it just may fail.

> t/pmc/signal...................Hangup

I saw that once too: looks like the test script got the signal.

leo

Jeff Clites

unread,
Oct 19, 2004, 5:01:31 AM10/19/04
to Perl 6 Internals
On Oct 19, 2004, at 12:42 AM, Leopold Toetsch wrote:

> Will Coleda <parrotbug...@parrotcode.org> wrote:
>
>> t/pmc/signal...................Hangup
>
> I saw that once too: looks like the test script got the signal.

That's what my patch from last week was supposed to fix--I'm surprised
it's still happening. We should currently be making sure not to kill
the harness.

(However, if there's another copy of parrot running--for instance,
stopped in a debugger somewhere--then that may get the signal
erroneously.)

JEff

0 new messages