Something went wrong with UTF-8 locales and B?  (Was working
until very
recently, patchlevel 32154 was still all Os.)  (Seems that
also Linux
and HP-UX have the exact same failure.)

-------- Original Message --------
Subject: Smoke [5.10.0] 32171 FAIL(F) OSF1 V5.1 (EV6/4 cpu)
Date: Tue, 23 Oct 2007 10:16:27 +0300 (EEST)
From: Jarkko Hietaniemi <jhicc.hut.fi>
To: smokers-reportsperl.org
CC: jhiiki.fi

Automated smoke report for 5.10.0 patch 32171
kosh.hut.fi: alpha EV6.7 (21264A) (EV6/4 cpu)
    on        OSF1 - V5.1
    using     cc version V6.5-011
    smoketime 10 hours 53 minutes (average 1 hour 48
minutes)

Summary: FAIL(F)

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

   32171     Configuration (common) -Dlocincpth=/p/include
-Dloclibpth=/p/lib
-----------
---------------------------------------------------------
O O F O O F
O O F O O F -Dcc=gcc -Dgccansipedantic
O O F O O F -Duseithreads
| | | | | +- LC_ALL = fi_FI.UTF-8 -DDEBUGGING
| | | | +--- PERLIO = perlio -DDEBUGGING
| | | +----- PERLIO = stdio  -DDEBUGGING
| | +------- LC_ALL = fi_FI.UTF-8
| +--------- PERLIO = perlio
+----------- PERLIO = stdio

Locally applied patches:
    DEVEL
    SMOKE32171

Failures: (common-args) -Dlocincpth=/p/include
-Dloclibpth=/p/lib
[fi_FI.UTF-8]
[fi_FI.UTF-8] -DDEBUGGING
[fi_FI.UTF-8] -Dcc=gcc -Dgccansipedantic
[fi_FI.UTF-8] -DDEBUGGING -Dcc=gcc -Dgccansipedantic
[fi_FI.UTF-8] -Duseithreads
[fi_FI.UTF-8] -DDEBUGGING -Duseithreads
    ../ext/B/t/optree_misc.t................FAILED 2

-- 
Report by Test::Smoke v1.19_84 build 991 running on perl
5.8.3
(Reporter v0.026 / Smoker v0.030)

On 23/10/2007, Jarkko Hietaniemi <jhiiki.fi> wrote:
> Something went wrong with UTF-8 locales and B?  (Was
working until very
> recently, patchlevel 32154 was still all Os.)  (Seems
that also Linux
> and HP-UX have the exact same failure.)

Should be fixed by #32177 already.