Skip to content

Unexpected failures in testsuite due to .ghci

Running the testsuite, I get e.g.

=====> 3171(normal) 375 of 2596 [0, 1, 0]
cd ./ghci/should_run && $MAKE -s --no-print-directory 3171    </dev/null >3171.run.stdout 2>3171.run.stderr
=====> bug1465(normal) 376 of 2596 [0, 1, 0]
cd ./typecheck/bug1465 && $MAKE -s --no-print-directory bug1465    </dev/null >bug1465.run.stdout 2>bug1465.run.stderr
Actual stdout output differs from expected:
--- ./ghci/should_run/3171.stdout.normalised	2010-10-07 13:20:16.000000000 +0200
+++ ./ghci/should_run/3171.run.stdout.normalised	2010-10-07 13:20:16.000000000 +0200
@@ -1 +1,3 @@
+ghci: warnings (except type defaulting and unused do-binds) on; MR off.
+(0.05 secs, 2799172 bytes)
 Interrupted.
*** unexpected failure for 3171(normal)

since it reads ~/.ghci.

I think -ignore-dot-ghci should be passed in the testsuite to avoid such gratuitous unexpected failures.

Trac metadata
Trac field Value
Version 7.1
Type Bug
TypeOfFailure OtherFailure
Priority normal
Resolution Unresolved
Component Test Suite
Test case
Differential revisions
BlockedBy
Related
Blocking
CC
Operating system
Architecture
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information