On 11/9/12 2:43 AM, Gerd Pokorra wrote:
Sorry there was a typing error.
The output of "prove t/op/gc-leaky-call.t" is:
[gz016@vdesk1 current.git]$ prove t/op/gc-leaky-call.t
t/op/gc-leaky-call.t .. 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.78 cusr
0.55 csys = 17.36 CPU)
Result: FAIL
[gz016@vdesk1 current.git]$
Since you're reporting problems with the alternate cores, you should
also report the results of this:
make test_prep
export HARNESS_VERBOSE=2
perl t/harness --gc-debug -b t/op/gc-leaky-call.t
perl t/harness --gc-debug -b t/op/gc-leaky-box.t
perl t/harness --gc-debug -r t/op/gc-leaky-call.t
perl t/harness --gc-debug -r t/op/gc-leaky-box.t
On Darwin, precede these calls with your equivalent to this:
export DYLD_LIBRARY_PATH=/Users/username/gitwork/parrot/blib/lib
... where /Users/username/gitwork/parrot is your top-level directory in
your parrot checkout.
HTH.
Thank you very much.
Jim Keenan
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
