#1393: t/compilers/pge/pge_examples.t: PASS by itself, FAIL during 'make smoke'
---------------------+------------------------------------------------------
Reporter: jkeenan | Owner:
Type: bug | Status: new
Priority: major | Milestone:
Component: testing | Version: 1.9.0
Severity: high | Keywords:
Lang: | Patch:
Platform: |
---------------------+------------------------------------------------------
Changes (by jkeenan):
* priority: normal => major
* severity: medium => high
Comment:
mikehh, thanks for that analysis.
Now, to make matters '''more''' confusing ...
In [http://smolder.plusthree.com/app/public_projects/report_details/31491
this Smolder test] run at r43392 (last change at r43382), the problems in
''t/compilers/pge/pge_examples.t'' have mysteriously fixed themselves.
{{{
$ perl t/harness --gc-debug t/compilers/pge/pge_examples.t
t/compilers/pge/pge_examples.t .. ok
All tests successful.
Files=1, Tests=2, 1 wallclock secs ( 0.01 usr 0.00 sys + 0.41 cusr
0.03 csys = 0.45 CPU)
Result: PASS
}}}
But now, I'm getting failures in ''t/library/test_more.t'':
{{{
$ perl t/harness --gc-debug t/library/test_more.t
t/library/test_more.t .. 1/108 src/gc/api.c:245: failed assertion
'PObj_is_PMC_TEST(obj)'
Backtrace - Obtained 32 stack frames (max trace depth is 32).
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0 [0x400e4572]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0(Parrot_confess+0x9a)
[0x400e46da]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0(Parrot_gc_mark_PMC_alive_fun+0x89)
[0x400f2b89]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0 [0x40287dcf]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0(Parrot_gc_mark_PMC_alive_fun+0x116)
[0x400f2c16]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0 [0x40287fe7]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0(Parrot_gc_mark_PMC_alive_fun+0x116)
[0x400f2c16]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0 [0x400f6dd9]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0 [0x400f50e2]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0 [0x400f53a5]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0 [0x400f28a8]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0 [0x400f4f7d]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0 [0x400f4df4]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0 [0x400f292b]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0 [0x400f32a8]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0(Parrot_str_new_COW+0x8f)
[0x400539af]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0 [0x4010ba36]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0 [0x40237aa0]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0 [0x400f7dec]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0 [0x400f8291]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0(Parrot_get_namespace_keyed+0xad)
[0x400f853d]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0(Parrot_oo_get_class+0x13f)
[0x4014fcff]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0 [0x4007a3c8]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0 [0x4015fc2e]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0 [0x4015e18f]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0 [0x401077bf]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0(Parrot_pcc_invoke_from_sig_object+0x1e9)
[0x400fdcc9]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0(Parrot_pcc_invoke_sub_from_c_args+0xd3)
[0x400fddd3]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0 [0x401576e0]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0 [0x401578ab]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0(do_sub_pragmas+0x1a2)
[0x40157b62]
/home/jimk/work/parrot/blib/lib/libparrot.so.1.9.0 [0x40157d37]
t/library/test_more.t .. Failed 48/108 subtests
Test Summary Report
-------------------
t/library/test_more.t (Wstat: 6 Tests: 60 Failed: 0)
Non-zero wait status: 6
Parse errors: Bad plan. You planned 108 tests but ran 60.
Files=1, Tests=60, 0 wallclock secs ( 0.04 usr 0.00 sys + 0.07 cusr
0.01 csys = 0.12 CPU)
Result: FAIL
}}}
Astute readers of my posts will recall that I reported the same failures
in a completely different ticket -- TT #473. In that ticket, where I am
trying to merge the ''tt473_remove_memcpy_aligned'' branch into trunk, I
got this error for a while, only to see it clear up and be replaced by
errors in ''t/compilers/pct/complete_workflow.t!''
We are clearly building up some massive technical debt here. I have not
been able to get a 100% `PASS` on `make test` in two weeks -- and this on
the least exotic platform with the least exotic compilation options. And
I have been unable to complete merges that should have been a slam dunk
because they were only removing unused code.
This is having a severe impact on what I can contribute to the Parrot
project. If I can't get a clear `PASS` on Linux/i386, I can't confidently
apply other contributors' patches. And I will have no confidence in
Parrot 2.0 until I can get a `PASS`.
So I'm upping the priority and severity on this ticket. Thank you very
much.
kid51
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1393#comment:16>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
