On Fri, Dec 07, 2007 at 08:45:03PM +0200, Allison Randal wrote: > jerry gay wrote: > >> > >looks good to me. commit away! > >nice work. > > I've got a clean report on our core platform targets, so committed in > r23574. As usual, please report any issues.
r23574 gives me failures in t/src/vtables.t and t/compilers/pge/perl6regex/context.t: Test Summary Report ------------------- t/configure/115-auto_warnings.t (Wstat: 0 Tests: 4 Failed: 0) TODO passed: 4 t/configure/124-auto_alignptrs-05.t (Wstat: 0 Tests: 21 Failed: 0) TODO passed: 20 t/configure/146-auto_snprintf-01.t (Wstat: 0 Tests: 31 Failed: 0) TODO passed: 30 t/compilers/pge/perl6regex/context.t (Wstat: 256 Tests: 20 Failed: 1) Failed test number(s): 6 Non-zero exit status: 1 t/src/intlist.t (Wstat: 0 Tests: 4 Failed: 0) TODO passed: 1-4 t/src/io.t (Wstat: 0 Tests: 20 Failed: 0) TODO passed: 16-17, 19 t/src/vtables.t (Wstat: 256 Tests: 4 Failed: 1) Failed test number(s): 4 Non-zero exit status: 1 Files=475, Tests=9741, 405 wallclock secs ( 2.87 usr 0.71 sys + 186.81 cusr 50.72 csys = 241.11 CPU) Result: FAIL Failed 2/475 test programs. 2/9741 subtests failed. make: *** [test] Error 255 $ Running "prove -v t/src/vtables.t" gives: $ prove -v t/src/vtables.t t/src/vtables...... 1..4 ok 1 - Parrot_new_vtable ok 2 - Parrot_clone_vtable not ok 3 - Parrot_destroy_vtable # TODO vtable not NULL after destroy # Failed (TODO) test (t/src/vtables.t at line 100) # got: 'ok # not ok # ' # expected: 'ok # ok # ' # './t/src/vtables_3' failed with exit code 0 not ok 4 - parrot_alloc_vtables # Failed test (t/src/vtables.t at line 142) # Exited with error code: [SIGNAL 139] # Received: # # Expected: # ok # ok # ok # # Looks like you failed 1 test of 4. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/4 subtests Test Summary Report ------------------- t/src/vtables.t (Wstat: 256 Tests: 4 Failed: 1) Failed test number(s): 4 Non-zero exit status: 1 Files=1, Tests=4, 1 wallclock secs ( 0.01 usr 0.00 sys + 0.95 cusr 0.16 csys = 1.12 CPU) Result: FAIL $ Running "prove -v t/compilers/pge/perl6regex/context.t" shows all tests passing. Running the harness directly with the --gc-debug flag (as 'make test' normally does) gives: $ perl t/harness --gc-debug t/compilers/pge/perl6regex/*.t t/compilers/pge/perl6regex/01-regex......ok t/compilers/pge/perl6regex/context.......1/20 # Failed test (t/compilers/pge/perl6regex/context.t at line 96) # Exited with error code: 139 # Received: # 0 # Segmentation fault (core dumped) # # Expected: # 0 # t/compilers/pge/perl6regex/context.......11/20 # Looks like you failed 1 test of 20. t/compilers/pge/perl6regex/context....... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/20 subtests Test Summary Report ------------------- t/compilers/pge/perl6regex/context.t (Wstat: 256 Tests: 20 Failed: 1) Failed test number(s): 6 Non-zero exit status: 1 Files=2, Tests=764, 7 wallclock secs ( 0.12 usr 0.00 sys + 7.05 cusr 0.24 csys = 7.41 CPU) Result: FAIL Failed 1/2 test programs. 1/764 subtests failed. $ I don't know if this last failure is related to the ccache/gc-debug failure I wrote about in RT#47970, but it sure looks like it. I do know that the context.t test passes with --gc-debug in r23573 but not in r23574. I'm on Kubuntu 7.10 x86. If I can supply more details, let me know. Pm
