#380: t/pmc/exceptionhandler.t - Bad plan. You planned 8 tests but ran 6
--------------------+-------------------------------------------------------
 Reporter:  mikehh  |        Type:  bug   
   Status:  new     |    Priority:  normal
Milestone:          |   Component:  core  
  Version:  trunk   |    Severity:  medium
 Keywords:  pmc     |        Lang:        
    Patch:          |    Platform:        
--------------------+-------------------------------------------------------

Comment(by mikehh):

 I was wrong - there was a failure in the test suite.

 Test Summary Report[[BR]]
 -------------------[[BR]]
 t/dynpmc/foo.t                            (Wstat: 256 Tests: 9 Failed:
 1)[[BR]]
   Failed test:  3[[BR]]
   Non-zero exit status: 1[[BR]]
 Files=396, Tests=11702, 362 wallclock secs ( 4.11 usr  1.10 sys + 137.80
 cusr 45.93 csys = 188.94 CPU)[[BR]]
 Result: FAIL[[BR]]


 I have had the following results:

 Linux i386  With --optimize flag - r37017:

 http://smolder.plusthree.com/app/public_projects/report_details/18353

 11,700 ok, 0 failed, 250 todo, 570 skipped and 0 unexpectedly succeeded


 Linux AMD64 (no --optimize flag) - r37017:

 http://smolder.plusthree.com/app/public_projects/report_details/18357

 11,703 ok, 0 failed, 250 todo, 570 skipped and 0 unexpectedly succeeded


 Linux i386 (no --optimize flag) - r37017:

 http://smolder.plusthree.com/app/public_projects/report_details/18361

 11,701 ok, 1 failed, 250 todo, 570 skipped and 0 unexpectedly succeeded


 I did a make realclean, perl Configure --test, make world, make smoke

 http://smolder.plusthree.com/app/public_projects/report_details/18362

 11,701 ok, 1 failed, 250 todo, 570 skipped and 0 unexpectedly succeeded


 This worries me a bit.

 Lots of tests - something seriously wrong - don't use it.

 In one situation we have - on the same platform - different test results
 with or without the optimize flag in use - BUT - only two test files out
 of 390 - three tests out of 11702.

 The test that fails passes on AMD64 (without the optimize which I haven't
 tested this week but was still failing last week - the optimize that is,
 but, a little further down the line).

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/380#comment:4>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets

Reply via email to