[EMAIL PROTECTED] wrote:
Automated smoke report for 5.9.4 patch 27938
kirk: Intel(R) Celeron(R) CPU 2.00GHz (GenuineIntel 1994MHz) (i686/1 cpu)
on linux - 2.6.15-20-386 [debian]
using cc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)
smoketime 17 hours 54 minutes (average 1 hour 7 minutes)
Summary: FAIL(X)
O = OK F = Failure(s), extended report at the bottom
X = Failure(s) under TEST but not under harness
? = still running or test results not (yet) available
Build failures during: - = unknown or N/A
c = Configure, m = make, M = make (after miniperl), t = make test-prep
27938 Configuration (common) none
----------- ---------------------------------------------------------
O O O O O O
O O O O O O -Duse64bitint
O O O O O O -Duselongdouble
O O O O O O -Dusemorebits
O O O O O O -Duseithreads
O O O O O O -Duseithreads -Duse64bitint
X O O O X O -Duseithreads -Duselongdouble
O O O O O O -Duseithreads -Dusemorebits
| | | | | +- LC_ALL = en_US.utf8 -DDEBUGGING
| | | | +--- PERLIO = perlio -DDEBUGGING
| | | +----- PERLIO = stdio -DDEBUGGING
| | +------- LC_ALL = en_US.utf8
| +--------- PERLIO = perlio
+----------- PERLIO = stdio
Locally applied patches:
SMOKE27938
Failures: (common-args) none
[stdio] -Duseithreads -Duselongdouble
Inconsistent test results (between TEST and harness):
../ext/threads/t/free.t.................FAILED--expected test 18, saw test
19
[perlio] -DDEBUGGING -Duseithreads -Duselongdouble
Inconsistent test results (between TEST and harness):
../ext/threads/t/free.t.................FAILED--expected test 15, saw test
16
What's happening above is that TEST cannot handle seeing tests come in
out of order, while harness can. I'm scanning Test::Harness::TAP a bit,
but it seems to be unspecified whether this is OK or not. Should TEST
care if the tests are reported out of order?
Steve Peters
[EMAIL PROTECTED]
