Howdy, here is the prove output with verbose option:
[gz016@vdesk1 current.git]$ prove -v t/op/gc-leaky-call.t t/op/gc-leaky-call.t .. # gms 1..3 not ok 1 - performed 0 (which should be >=1) GC collect runs ok 2 - performed 5 (which should be >=1) GC mark runs ok 3 - allocated 0 (which should be <= 6_000_000) bytes of memory Failed 1/3 subtests Test Summary Report ------------------- t/op/gc-leaky-call.t (Wstat: 0 Tests: 3 Failed: 1) Failed test: 1 Files=1, Tests=3, 17 wallclock secs ( 0.03 usr 0.00 sys + 16.87 cusr 0.53 csys = 17.43 CPU) Result: FAIL [gz016@vdesk1 current.git]$ prove -v t/op/gc-leaky-box.t t/op/gc-leaky-box.t .. 1..3 not ok 1 - performed 0 (which should be >=1) GC collect runs ok 2 - performed 5 (which should be >=1) GC mark runs ok 3 - allocated 0 (which should be <= 3_000_000) bytes of memory Failed 1/3 subtests Test Summary Report ------------------- t/op/gc-leaky-box.t (Wstat: 0 Tests: 3 Failed: 1) Failed test: 1 Files=1, Tests=3, 44 wallclock secs ( 0.03 usr 0.00 sys + 42.62 cusr 0.65 csys = 43.30 CPU) Result: FAIL [gz016@vdesk1 current.git]$ Gerd Am Freitag, den 09.11.2012, 12:03 -0800 schrieb Jonathan "Duke" Leto: > Howdy, > > Can you show us the verbose output, i.e. : > > prove -v t/op/gc-leaky-call.t > > Thanks! > > Duke > > On Thu, Nov 8, 2012 at 11:43 PM, Gerd Pokorra <[email protected]> > wrote: > prove t/op/gc-leaky-call.t > > > > -- > Jonathan "Duke" Leto <[email protected]> > Leto Labs LLC http://labs.leto.net > 209.691.DUKE http://dukeleto.pl > _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
