#254: t/native_pbc/number.t: New failure on some platforms
---------------------+------------------------------------------------------
Reporter: jkeenan | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: none | Version:
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
---------------------+------------------------------------------------------
Comment(by jkeenan):
This failure was reported on x86_64 with ICC in a different file in the
same directory:
{{{
perl t/harness --gc-debug --running-make-test t/native_pbc/integer.t
t/native_pbc/integer....
t/native_pbc/integer....NOK 1/1# Failed test 'i386 32 bit opcode_t, 32
bit intval'
# at t/native_pbc/integer.t line 57.
# Exited with error code: 1
# Received:
# PackFile_unpack segment 'BYTECODE_i1.pasm' directory length 0 length in
file 0 needed 4 for unpack
# PackFile_unpack segment 'FIXUP_i1.pasm' directory length 3 length in
file 3 needed 4 for unpack
# Constant_unpack: Unrecognized type '' during unpack!
# PackFile_unpack segment 'CONSTANT_i1.pasm' failed
# Subroutine returned a NULL address
# current instr.: '(null)' pc -1 ((unknown file):-1)
#
# Expected:
# 270544960
# May need to regenerate t/native_pbc/integer_1.pbc; read test file
# Looks like you failed 1 test of 1.
t/native_pbc/integer....dubious
Test returned status 1 (wstat 256, 0x100)
DIED. FAILED test 1
Failed 1/1 tests, 0.00% okay
Failed Test Stat Wstat Total Fail List of Failed
-------------------------------------------------------------------------------
t/native_pbc/integer.t 1 256 1 1 1
Failed 1/1 test scripts. 1/1 subtests failed.
Files=1, Tests=1, 0 wallclock secs ( 0.14 cusr + 0.06 csys = 0.20 CPU)
Failed 1/1 test programs. 1/1 subtests failed.
}}}
This file also underwent revisions today.
{{{
$ svn diff -r {2009-01-27} t/native_pbc/integer.t
Index: t/native_pbc/integer.t
===================================================================
--- t/native_pbc/integer.t (revision 36042)
+++ t/native_pbc/integer.t (working copy)
@@ -7,7 +7,7 @@
use lib qw( . lib ../lib ../../lib );
use Test::More;
-use Parrot::Test skip_all => 'ongoing PBC format changes';
+use Parrot::Test tests => 1;
=head1 NAME
@@ -25,7 +25,7 @@
=begin comment
-s. t/native_pbc/number.t for additional comments
+see t/native_pbc/number.t for additional comments
Test files on different architectures are generated by:
@@ -46,10 +46,11 @@
# execute the file t/native_pbc/integer_1.pbc
#
# HEADER => [
-# wordsize = 4 (interpreter's wordsize = 4)
-# int_size = 4 (interpreter's INTVAL size = 4)
-# byteorder = 0 (interpreter's byteorder = 0)
-# floattype = 0 (interpreter's NUMVAL_SIZE = 8)
+# wordsize = 4 (interpreter's wordsize/INTVAL = 4/4)
+# byteorder = 0 (interpreter's byteorder = 0)
+# floattype = 0 (interpreter's NUMVAL_SIZE = 8)
+# parrot-version 0.9.0, bytecode-version 3.34
+# UUID type = 0, UUID size = 0
# no endianize, no opcode, no numval transform
# dirformat = 1
# ]
@@ -57,9 +58,9 @@
or diag "May need to regenerate t/native_pbc/integer_1.pbc; read test
file";
# Formerly following tests had been set up:
-# pasm_output_is(undef, '270544960', "PPC BE 32 bit opcode_t, 32 bit
intval");
-# pasm_output_is(undef, '270544960', "little-endian 64-bit tru64");
-# pasm_output_is(undef, '270544960', "big-endian 64-bit irix");
+# pbc_output_is(undef, '270544960', "PPC BE 32 bit opcode_t, 32 bit
intval");
+# pbc_output_is(undef, '270544960', "little-endian 64-bit tru64");
+# pbc_output_is(undef, '270544960', "big-endian 64-bit irix");
# Local Variables:
# mode: cperl
}}}
Here is the log message for that revision:
{{{
------------------------------------------------------------------------
r36160 | rurban | 2009-01-29 16:09:59 -0500 (Thu, 29 Jan 2009) | 7 lines
[test] native_pbc:
- Adapt number and integer to new pbc format, string not yet
- Create new reference pbc's for i386 32 bit opcode_t, 32 bit intval
- Will need other platforms pbc's.
}}}
I should note that this test did not fail for me on Darwin/PPC.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/254#comment:1>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
