Little threading glitch on Linux/Sparc when perlio isn't available.
Make log is attached, but there's not much interesting in it.

Same problem back at 13911, so at least its no worse.  The warnings
are gone now. :)
http:[EMAIL PROTECTED]/msg00374.html

This is the Linux/Sparc machine in the SourceForge compile farm.


Automated smoke report for patch 15089 on linux - 2.2.18pre21
          v1.12      using cc version 2.95.2 20000220 (Debian GNU/Linux)
O = OK
F = Failure(s), extended report at the bottom
? = still running or test results not (yet) available
Build failures during:       - = unknown
    c = Configure, m = make, t = make test-prep

         Configuration
-------  --------------------------------------------------------------------
O O O O -Uuseperlio
O O O O -Duseperlio
O O O O -Duseperlio -Duse64bitint
O O O O -Duseperlio -Duse64bitall
O O O O -Duseperlio -Duselongdouble
O O O O -Duseperlio -Dusemorebits
O O O O -Duseperlio -Duse64bitall -Duselongdouble
F F F F -Dusethreads -Duseithreads -Uuseperlio
O O O O -Dusethreads -Duseithreads -Duseperlio
O O O O -Dusethreads -Duseithreads -Duseperlio -Duse64bitint
O O O O -Dusethreads -Duseithreads -Duseperlio -Duse64bitall
O O O O -Dusethreads -Duseithreads -Duseperlio -Duselongdouble
O O O O -Dusethreads -Duseithreads -Duseperlio -Dusemorebits
O O O O -Dusethreads -Duseithreads -Duseperlio -Duse64bitall -Duselongdouble
| | | +- PERLIO = perlio -DDEBUGGING
| | +--- PERLIO = stdio  -DDEBUGGING
| +----- PERLIO = perlio
+------- PERLIO = stdio

Failures:

linux        stdio            -Dusethreads -Duseithreads -Uuseperlio
    ext/threads/t/stress_cv.............FAILED at test 65
    ext/threads/t/stress_re.............FAILED at test 65

linux        perlio           -Dusethreads -Duseithreads -Uuseperlio
    ext/threads/t/stress_cv.............FAILED at test 54
    ext/threads/t/stress_re.............FAILED at test 65
    ext/threads/t/stress_string.........FAILED at test 56
.../ext/threads/t/stress_cv........Confused test output: test 34 answered after test 
46LED test 51

linux        stdio            -DDEBUGGING -Dusethreads -Duseithreads -Uuseperlio
    ext/threads/t/stress_cv.............FAILED at test 65
    ext/threads/t/stress_string.........FAILED at test 51

linux        perlio           -DDEBUGGING -Dusethreads -Duseithreads -Uuseperlio
    ext/threads/t/stress_cv.............FAILED at test 65
    ext/threads/t/stress_re.............FAILED at test 61
    ext/threads/t/stress_string.........FAILED at test 55
.../ext/threads/t/stress_cv........Confused test output: test 34 answered after test 
42LED test 57



MANIFEST did not declare ext/I18N/Langinfo/fallback.c

-- 

Michael G. Schwern   <[EMAIL PROTECTED]>    http://www.pobox.com/~schwern/
Perl Quality Assurance      <[EMAIL PROTECTED]>         Kwalitee Is Job One
I know you get this a lot, but you're breathtaking, like a vision of
simplicity

Attachment: mktest.log.gz
Description: Binary data

Reply via email to