id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc	lang	patch	platform
489	t/tools/ops2pm/*.t:  Failures in 3 test files	jkeenan	jkeenan	"Running `perl Configure.pl --test` at r37676 this morning, I got the following failures in the build tools tests on two different OSes:
{{{
t/tools/ops2pm/09-prepare_real_ops.............1/? op load_language_s: sequence mismatch: ops.num 235 vs. core.ops 1245 at /Users/jimk/work/parrot/lib/Parrot/Ops2pm.pm line 248.
# Looks like you planned 38 tests but only ran 16.
# Looks like your test died just after 16.
t/tools/ops2pm/09-prepare_real_ops............. Dubious, test returned 255 (wstat 65280, 0xff00)
 Failed 22/38 subtests 
t/tools/ops2pm/10-print_module.................3/? op load_language_s: sequence mismatch: ops.num 235 vs. core.ops 1245 at /Users/jimk/work/parrot/lib/Parrot/Ops2pm.pm line 248.
# Looks like you planned 42 tests but only ran 16.
# Looks like your test died just after 16.
t/tools/ops2pm/10-print_module................. Dubious, test returned 255 (wstat 65280, 0xff00)
 Failed 26/42 subtests 
t/tools/ops2pm/11-print_h......................1/? op load_language_s: sequence mismatch: ops.num 235 vs. core.ops 1245 at /Users/jimk/work/parrot/lib/Parrot/Ops2pm.pm line 248.
# Looks like you planned 23 tests but only ran 16.
# Looks like your test died just after 16.
t/tools/ops2pm/11-print_h...................... Dubious, test returned 255 (wstat 65280, 0xff00)
 Failed 7/23 subtests 
t/pharness/01-default_tests....................ok     
t/pharness/02-get_test_prog_args...............ok     
t/pharness/03-handle_long_options..............ok     
t/pharness/04-Usage............................ok   

Test Summary Report
-------------------
t/tools/ops2pm/09-prepare_real_ops         (Wstat: 65280 Tests: 16 Failed: 0)
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 38 tests but ran 16.
t/tools/ops2pm/10-print_module             (Wstat: 65280 Tests: 16 Failed: 0)
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 42 tests but ran 16.
t/tools/ops2pm/11-print_h                  (Wstat: 65280 Tests: 16 Failed: 0)
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 23 tests but ran 16.
Files=37, Tests=941, 115 wallclock secs ( 1.19 usr  0.97 sys + 71.85 cusr 11.18 csys = 85.19 CPU)
Result: FAIL
Failed 3/37 test programs. 0/941 subtests failed.
}}}
Since at least the first failure reported occurred in a test where we were testing what happens when a limited selection of op codes are used, this may be fallout from r37601, in which we removed the `--pmc` option from ''Configure.pl''.  At that time, we adjusted the tests in ''t/tools/pmc2c''.

But since I ran the build tools tests at that time and did '''not''' get these test failures, I can't be entirely sure.  It may also be the case that recent removal of certain PMCs and op codes has not been accompanied by renumbering of ops and PMCs.

I don't think these failures are having an impact '''yet''' on the building of Parrot, but further investigation is needed.

Thank you very much.[[BR]]
kid51"	bug	closed	normal		none		medium	fixed	ops ops2pm	allison@…		applied	all