List Info

Thread: Is anyone paying attention to these smoke failures?




Is anyone paying attention to these smoke failures?
user name
2007-09-24 02:03:32
Hi,

Smokes for 5.10 on FreeBSD have been failing for a long
while now, and
it even seems to be getting worse. Is anyone paying
attention to
these failures?

If not, I might as well stop smoking FreeBSD and use the
system
capacity for something more useful.

-- Johan

Automated smoke report for 5.10.0 patch 31945
smokey.squirrel.nl: Intel(R) Core(TM)2 CPU          6300 

1.86GHz (i386/1 cpu)
    on        freebsd - 6.2-RELEASE
    using     cc version 3.4.6 [FreeBSD] 20060305
    smoketime 8 hours 10 minutes (average 1 hour 1 minute)

Summary: FAIL(XF)

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

   31945     Configuration (common) none
-----------
---------------------------------------------------------
O F O O O O 
X O X X X O -Duse64bitint
X O F X O O -Duseithreads
X O O O O O -Duseithreads -Duse64bitint
| | | | | +- LC_ALL = nl_NL.UTF-8 -DDEBUGGING
| | | | +--- PERLIO = perlio -DDEBUGGING
| | | +----- PERLIO = stdio  -DDEBUGGING
| | +------- LC_ALL = nl_NL.UTF-8
| +--------- PERLIO = perlio
+----------- PERLIO = stdio

Locally applied patches:
    DEVEL
    SMOKE31945

Failures: (common-args) none
[perlio] 
[nl_NL.UTF-8] -Duseithreads
    ../lib/Benchmark.t......................FAILED 13

[stdio] -Duse64bitint
Inconsistent test results (between TEST and harness):
    ../lib/Benchmark.t......................FAILED at test
127

[nl_NL.UTF-8] -Duse64bitint
[stdio/perlio] -DDEBUGGING -Duse64bitint
[stdio] -DDEBUGGING -Duseithreads
Inconsistent test results (between TEST and harness):
    ../lib/Benchmark.t......................FAILED at test
13

[stdio] -Duseithreads
[stdio] -Duseithreads -Duse64bitint
Inconsistent test results (between TEST and harness):
    ../lib/Benchmark.t......................FAILED at test
126

Compiler messages(gcc):
regcomp.c: In function `S_regatom':
regcomp.c:6833: warning: 'len' might be used uninitialized
in this function
mg.c: In function `Perl_sighandler':
mg.c:2910: warning: null format string
pp_sys.c: In function `Perl_pp_die':
pp_sys.c:504: warning: null format string
pp_sys.c:307: warning: 'S_emulate_eaccess' defined but not
used
util.c: In function `Perl_get_hash_seed':
util.c:5265: warning: implicit declaration of function
`strtoull'
mg.c: In function `Perl_magic_set':
mg.c:2639: warning: implicit declaration of function
`atoll'

-- 
Report by Test::Smoke v1.19_86 build 1030 running on perl
5.8.8
(Reporter v0.027 / Smoker v0.032)



Re: Is anyone paying attention to these smoke failures?
user name
2007-09-24 03:55:23
On 24/09/2007, Johan Vromans <jvromanssquirrel.nl> wrote:
> Hi,
>
> Smokes for 5.10 on FreeBSD have been failing for a long
while now, and
> it even seems to be getting worse. Is anyone paying
attention to
> these failures?

Benchmark.t can fail on heavily loaded or otherwise slow
systems. Is
this the case for you ?

[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )