32-bit Linux perf failures
Mateusz Kowalczyk
fuuzetsu at fuuzetsu.co.uk
Thu Feb 20 01:39:45 UTC 2014
Greetings,
I just ran validate with current HEAD
(2b34947b60069e51abfcada9c45a6d7b590f5a2b) and I have quite a few perf
failures. Perhaps these need tweaking? I know that 32-bit numbers were
neglected in the past. The Haddock numbers have been complaining for a
few weeks now but I think everything else is fairly new.
Here is the end of the log:
Unexpected results from:
TEST="T876 T7954 T8766 T1969 T5631 T783 T3294 haddock.Cabal
haddock.compiler haddock.base T3924"
OVERALL SUMMARY for test run started at Thu Feb 20 00:54:28 2014 GMT
0:18:11 spent to go through
3903 total tests, which gave rise to
15265 test cases, of which
11699 were skipped
28 had missing libraries
3469 expected passes
58 expected failures
3 caused framework failures
0 unexpected passes
11 unexpected failures
Unexpected failures:
../../libraries/base/tests T8766 [stat too good] (normal)
callarity/perf T3924 [stat too good] (normal)
perf/compiler T1969 [stat too good] (normal)
perf/compiler T3294 [stat too good] (normal)
perf/compiler T5631 [stat too good] (normal)
perf/compiler T783 [stat too good] (normal)
perf/haddock haddock.Cabal [stat too good] (normal)
perf/haddock haddock.base [stat not good enough] (normal)
perf/haddock haddock.compiler [stat too good] (normal)
perf/should_run T7954 [stat too good] (normal)
perf/should_run T876 [stat too good] (normal)
--
Mateusz K.
More information about the ghc-devs
mailing list