More validate failures

Daniel Fischer at
Thu Apr 24 15:54:22 UTC 2014

Running the full testsuite (sh validate --testsuite-only --slow), I get a lot 
of unexpected failures (45 on this run).


fails due to

Compile failed (status 256) errors were:
[1 of 1] Compiling Main             ( tcrun045.hs, tcrun045.o )

    Illegal implict parameter ‘?imp::Int’
    In the context: (?imp::Int)
    While checking the super-classes of class ‘D’
    In the class declaration for ‘D’

and 6.12, 7.0, 7.2 and 7.8 refuse the file with the same error, only 7.4 and 
7.6 accept it. Is that a regression or are 7.4 and 7.6 wrong and it shouldn't 
have compiled?

Then I get a lot of optllvm failures, like

=====> GMapAssoc(optllvm) 891 of 3955 [0, 8, 0] 
cd ./indexed-types/should_run && '/home/dafis/GHC/virgo/bindisttest/install   
dir/bin/ghc' -fforce-recomp -dcore-lint -dcmm-lint -dno-debug-output -no-user-
package-db -rtsopts -ignore-dot-ghci -fno-ghci-history -o GMapAssoc 
GMapAssoc.hs -O -fllvm -package containers  >GMapAssoc.comp.stderr 2>&1
cd ./indexed-types/should_run && ./GMapAssoc    </dev/null 
> 2>
/bin/sh: Zeile 1: 21331 Speicherzugriffsfehler  ./GMapAssoc < /dev/null > 2>
Wrong exit code (expected 0 , actual 139 )


*** unexpected failure for GMapAssoc(optllvm)


=====> qq007(optllvm) 1161 of 3955 [0, 10, 0] 
cd ./quasiquotation/qq007 && $MAKE -s --no-print-directory TH_QQ
cd ./quasiquotation/qq007 && '/home/dafis/GHC/virgo/bindisttest/install   
dir/bin/ghc' -fforce-recomp -dcore-lint -dcmm-lint -dno-debug-output -no-user-
package-db -rtsopts -ignore-dot-ghci -fno-ghci-history --make  Test -O -fllvm 
-v0  >qq007.comp.stderr 2>&1
/bin/sh: Zeile 1: 25528 Speicherzugriffsfehler  
'/home/dafis/GHC/virgo/bindisttest/install   dir/bin/ghc' -fforce-recomp -
dcore-lint -dcmm-lint -dno-debug-output -no-user-package-db -rtsopts -ignore-
dot-ghci -fno-ghci-history --make Test -O -fllvm -v0 > qq007.comp.stderr 2>&1
Compile failed (status 35584) errors were:

*** unexpected failure for qq007(optllvm)

which I don't know what to make of, other optllvm tests work fine. Has anybody 
an idea what might cause those?

T6145 fails to compile with a type error and a missing argument to the `MG` 
constructor. Apparently the API changed but the test was not updated.

T8639_api has unexpected stdout, the type is printed as `Bool` instead of the 
expected `GHC.Types.Bool`, I guess one should update the expected output, but 
maybe the type should be printed qualified?

=====> T4891(normal) 1610 of 3955 [0, 14, 0] 
cd ./ghc-api/T4891 && $MAKE -s --no-print-directory T4891    </dev/null 
> 2>
Wrong exit code (expected 0 , actual 2 )


T4891.hs:23:19: Module ‘PrelNames’ does not export ‘iNTERACTIVE’
gmake[2]: *** [T4891] Fehler 1

*** unexpected failure for T4891(normal)

T3064 and T6048 allocate slightly more than they are allowed to (about 1% 
resp. 0.15% too much). Generally, I have the impression that whoever decides 
the 64-bit Linux allocation numbers has a system where the figures 
aresystematically lower than on mine, maybe the expected numbers should be 
given a bit higher.

joao-circular fails the optllvm way with unexpected stdout:

Actual stdout output differs from expected:
--- ./programs/joao-circular/joao-circular.stdout	2014-04-24 
11:18:07.363987627 +0200
+++ ./programs/joao-circular/	2014-04-24 
14:27:38.927486429 +0200
@@ -68,13 +68,6 @@
 PUSHa "recfact" 2
 PUSHa "x" 2
-PUSHa "x" 1
-PUSHa "x" 2
-PUSHi 1
-CALL "recfact"
 C_Ident_1 "end_if_1":
@@ -83,4 +76,4 @@
 Detected Semantic Errors:
 [C_E_Name_AD_1 (C_Ident_1 "a")]
+[C_E_T_NC_1 C_Errortype_1 C_Inttype_1,C_E_T_while_1,C_E_T_BOP_1,C_E_T_NC_1 
C_Errortype_1 C_Errortype_1,C_E_T_BOP_1,C_E_T_NC_1 C_Errortype_1 
C_Errortype_1,C_E_T_BOP_1,C_E_T_if_t_e_1,C_E_T_BOP_1,C_E_T_NC_1 C_Errortype_1 
C_Inttype_1,C_E_T_NC_1 C_Errortype_1 C_Errortype_1,C_E_T_BOP_1]
*** unexpected failure for joao-circular(optllvm)

which I have no idea how to interpret.

T7919 (optllvm) fails to compile. The ghci way, although it passed,  uses a 
lot of memory (~ 2.5 G), temporarily froze my box, and got my browser OOM-
killed. The other ways also use a lot of memory (~1.1 G - 1.7 G). While it 
looks as though it is to be expected that the test uses a fair bit of memory, 
perhaps it should not use quite as much. If somebody more knowledgeable looks 
at it that might be good.

simplCore/should_compile/spec001 fails due to unexpected stdout, the `-fno-
warn-amp`  flag is deprecated, the pragma should be removed probably.

arr016 (optllvm) failed with what looks serious:

=====> arr016(optllvm) 3092 of 3955 [0, 32, 0] 
cd ./array/should_run && '/home/dafis/GHC/virgo/bindisttest/install   
dir/bin/ghc' -fforce-recomp -dcore-lint -dcmm-lint -dno-debug-output -no-user-
package-db -rtsopts -ignore-dot-ghci -fno-ghci-history -o arr016 arr016.hs -O 
-fllvm   >arr016.comp.stderr 2>&1
cd ./array/should_run && ./arr016    </dev/null > 
/bin/sh: Zeile 1: 23929 Abgebrochen             ./arr016 < /dev/null > 2>
Wrong exit code (expected 0 , actual 134 )

arr016: internal error: MUT_ARR_PTRS_DIRTY object entered!
    (GHC version 7.9.20140424 for x86_64_unknown_linux)
    Please report this as a GHC bug:

*** unexpected failure for arr016(optllvm)

T7653(ghci) managed to get my browser OOM-killed again (yes, I was naive 
enough to restart it), using ~2.7 G of memory. And the test timed out - also 
when running only T7653 without the browser to compete for the memory. The 
threaded1 way uses even more memory (~2.9 G), other ways much, but not that 

posix002(threaded2) failed with

+posix002: failed to create OS thread: Resource temporarily unavailable
*** unexpected failure for posix002(threaded2)

but that isn't replicable running the test alone.

More information about the ghc-devs mailing list