#989: t/compilers/tge/grammar.t:  FAIL under 'make test', but passes with
'prove':  Darwin
---------------------+------------------------------------------------------
 Reporter:  jkeenan  |       Owner:  jkeenan        
     Type:  bug      |      Status:  assigned       
 Priority:  normal   |   Milestone:                 
Component:  testing  |     Version:  1.5.0          
 Severity:  medium   |    Keywords:  SIGNAL gc-debug
     Lang:           |       Patch:                 
 Platform:  darwin   |  
---------------------+------------------------------------------------------
Changes (by jkeenan):

 * cc: cotto, darbelo, dukeleto (added)
  * owner:  => jkeenan
  * status:  new => assigned


Comment:

 Replying to [comment:4 jkeenan]:

 This bug appears to have cleared up.  Observed at r41167:
 {{{
 $ perl t/harness --gc-debug t/compilers/tge/grammar.t
 t/compilers/tge/grammar.t .. 3/3
 not ok 3 - two rules of the same name can apply to the same node, when
 called with a different dummy type # TODO unresolved bug
 t/compilers/tge/grammar.t .. ok
 All tests successful.
 Files=1, Tests=3,  5 wallclock secs ( 0.08 usr  0.04 sys +  2.38 cusr
 0.36 csys =  2.86 CPU)
 Result: PASS
 }}}
 See also
 [http://smolder.plusthree.com/app/public_projects/report_details/27061
 this Smolder report on Darwin/PPC].

 Unfortunately, I cannot yet say '''when''' it cleared up or '''why''' it
 cleared up.  I '''can''' say that my best estimate of the point of failure
 is that it occurred at r41087, when
 ''config/gen/platform/darwin/hires_timer.c'' was introduced.  But since
 the build was broken from r41081 (''Merge pluggable_runcore branch into
 trunk.'') until approx. r41087, I cannot pinpoint the failure as I
 normally would.

 So I am going to first take this ticket, cc-ing contributors who I believe
 are interested in the hi-res timer issue, and then close it.  And then
 hope that it stays closed.

 Thank you very much.[[BR]]
 kid51

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/989#comment:5>
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