On 9/29/05, via RT Andy Dougherty <[EMAIL PROTECTED]> wrote:
> # '
> # expected: '3 * 5 == 15!
> # '
> # './parrot --gc-debug
> "/home/doughera/src/parrot/parrot-andy/t/op/gc_13.pir"' failed with exit code
> 131
> # Looks like you failed 1 test of 22.
this same test fails on win32, however the error message is less enlightening:
> perl t/harness t/op/gc.t
t/op/gc....ok 12/22
t/op/gc....NOK 13# Failed test (t/op/gc.t at line 279)
# got: '3 * 5 == 15!
# Can't spawn ".\parrot.exe
"D:\usr\local\parrot-bug\trunk\t\op\gc_13.pir"": Bad file descriptor
at lib/Parrot/Test.pm line 238.
# '
# expected: '3 * 5 == 15!
# '
# '.\parrot.exe "D:\usr\local\parrot-bug\trunk\t\op\gc_13.pir"'
failed with exit code 255
t/op/gc....ok 22/22# Looks like you failed 1 test of 22.
t/op/gc....dubious
Test returned status 1 (wstat 256, 0x100)
DIED. FAILED test 13
Failed 1/22 tests, 95.45% okay
Failed Test Stat Wstat Total Fail Failed List of Failed
-------------------------------------------------------------------------------
t/op/gc.t 1 256 22 1 4.55% 13
Failed 1/1 test scripts, 0.00% okay. 1/22 subtests failed, 95.45% okay.
perhaps a fix will affect both platforms, and the method used to fix
this problem may be applied to the few other windows bugs with the
same cryptic message.
~jerry
