develooper Front page | perl.perl5.porters | Postings from March 2011

(locales) Re: Smoke [5.13.10] v5.13.10-384-g3dfaac4 FAIL(F) openbsd4.8 (i386/1 cpu)

Thread Previous | Thread Next
From:
Karl Williamson
Date:
March 12, 2011 17:33
Subject:
(locales) Re: Smoke [5.13.10] v5.13.10-384-g3dfaac4 FAIL(F) openbsd4.8 (i386/1 cpu)
Message ID:
4D7C1E71.7080705@khwilliamson.com
On 03/12/2011 11:12 AM, Steven Schubiger wrote:
> Automated smoke report for 5.13.10 patch 3dfaac447d030f911d146c3ae56b9dba63ce9dd4 v5.13.10-384-g3dfaac4
> p5openbsd: AMD Athlon(tm) Processor ("AuthenticAMD" 686-class, 256KB L2 cache) (909 MHz) (i386/1 cpu)
>      on        openbsd - 4.8
>      using     cc version 4.2.1 20070719
>      smoketime 17 hours 37 minutes (average 2 hours 12 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
>
> v5.13.10-384-g3dfaac4  Configuration (common) none
> ----------- ---------------------------------------------------------
> F F F F
> F F F F     -Duse64bitint
> F F F F     -Duseithreads
> F F F F     -Duseithreads -Duse64bitint
> | | | +----- PERLIO = perlio -DDEBUGGING
> | | +------- PERLIO = stdio  -DDEBUGGING
> | +--------- PERLIO = perlio
> +----------- PERLIO = stdio
>
>
> Locally applied patches:
>      uncommitted-changes
>      SMOKE3dfaac447d030f911d146c3ae56b9dba63ce9dd4
>
> Failures: (common-args) none
> [stdio/perlio]
> [stdio/perlio] -Duse64bitint
>      ../t/re/charset.t...........................................FAILED
>          1621-1624, 1629-1632, 1645-1648, 1657-1660
>          1905-1908, 1917-1920, 1941-1944, 1961-1964



I have logged in to this box and it appears that the charset.t failures 
are due to an improper C locale there!   I confirmed this by writing a 
tiny C program and experimenting.

I don't know how to proceed with this.  The C locale is supposed to be 
the same everywhere, and so I thought it was safe to use it in testing, 
but apparently not.  I see several options:

1) Skip this test on this platform, assuming the smoker is 
representative of it.

2) Assume that locale is working well enough to do a a sanity check at 
the beginning of the platform, and if it fails don't test locale

3) skip testing locale altogether.

Ideas welcome


Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About