On 7 Dec 2007, at 16:32, chromatic wrote:
On Friday 07 December 2007 05:23:39 Allison Randal wrote:
I'm about to turn on the concurrency scheduler runloop in Parrot
trunk.
Before I do, I'd like test results on as many platforms as possible
(especially Windows, since it doesn't use POSIX threads).
To test it, edit src/inter_create.c and uncomment the two lines that
start with 'Parrot_cx...". Then run 'make test' and let me know if it
fails any tests that passed before.
On Ubuntu 7.10:
[snip]
On Debian 4.0
Test Summary Report
-------------------
t/configure/115-auto_warnings.t (Wstat: 0 Tests: 4 Failed: 0)
TODO passed: 4
t/configure/124-auto_alignptrs-05.t (Wstat: 0 Tests: 21 Failed:
0)
TODO passed: 20
t/configure/146-auto_snprintf-01.t (Wstat: 0 Tests: 31 Failed:
0)
TODO passed: 30
t/src/intlist.t (Wstat: 0 Tests: 4 Failed: 0)
TODO passed: 1-4
t/src/io.t (Wstat: 0 Tests: 20 Failed:
0)
TODO passed: 16-17, 19
t/src/vtables.t (Wstat: 256 Tests: 4
Failed: 1)
Failed test number(s): 4
Non-zero exit status: 1
Files=475, Tests=9747, 488 wallclock secs ( 0.61 usr 4.38 sys + 75.52
cusr 169.41 csys = 249.92 CPU)
Result: FAIL
Failed 1/475 test programs. 1/9747 subtests failed.
make: *** [test] Error 255
But on Mac OS 10.5 I get random hangs. First at
t/op/01-parse_ops..............................287/335
for about ten minutes until I interrupted it and then
t/op/string_cs.................................1/50
for another ten or so minutes.
--
Andy Armstrong, Hexten
