HEAD failing

Simon Peyton Jones simonpj at microsoft.com
Thu May 19 12:17:07 UTC 2016


=====> T8308(normal) 1 of 1 [0, 0, 0] 
cd /tmp/ghctest/kZl5Ju/1/2/3/./rts/T8308/T8308 && $MAKE -s --no-print-directory T8308    </dev/null > T8308.run.stdout 2> T8308.run.stderr
Actual stdout output differs from expected:
--- /tmp/ghctest/kZl5Ju/1/2/3/./rts/T8308/T8308/T8308.stdout.normalised	2016-05-19 13:16:54.915694378 +0100
+++ /tmp/ghctest/kZl5Ju/1/2/3/./rts/T8308/T8308/T8308.run.stdout.normalised	2016-05-19 13:16:54.915694378 +0100
@@ -1 +1 @@
-1
+8
*** unexpected failure for T8308(normal)

Unexpected results from:
TEST="T8308"

OVERALL SUMMARY for test run started at Thu May 19 13:16:53 2016 BST
 0:00:02 spent to go through
       1 total tests, which gave rise to
       1 test cases, of which
       0 were skipped

       0 had missing libraries
       0 expected passes
       0 expected failures

       0 caused framework failures
       0 unexpected passes
       1 unexpected failures
       0 unexpected stat failures

Unexpected failures:
   /tmp/ghctest/kZl5Ju/1/2/3/./rts/T8308/T8308  T8308 [bad stdout] (normal)

simonpj at cam-05-unx:~/5builds/HEAD-4/testsuite/tests$

|  -----Original Message-----
|  From: Ben Gamari [mailto:ben at well-typed.com]
|  Sent: 19 May 2016 13:16
|  To: Simon Peyton Jones <simonpj at microsoft.com>; ghc-devs <ghc-
|  devs at haskell.org>
|  Subject: Re: HEAD failing
|  
|  Simon Peyton Jones <simonpj at microsoft.com> writes:
|  
|  > Devs,
|  > I’m getting this on a clean build of HEAD on Linux
|  >
|  > Unexpected failures:
|  >
|  >    /tmp/ghctest/0MzM7D/1/2/3/./rts/T11108       T11108 [bad stdout]
|  (normal)
|  >
|  >    /tmp/ghctest/0MzM7D/1/2/3/./rts/T8308/T8308  T8308 [bad stdout]
|  > (normal) Two things
|  >
|  > ·         would it be possible to remove the long /tmp/blah prefix?
|  >
|  Thomas argued that it is convenient to be able to cut-and-paste the
|  path to a failing testcase. That being said, on balance I agree that
|  it is a bit too noisy to be worth the convenience.
|  
|  > ·         What’s wrong with these two rts tests?  I see that #11108
|  already reports the failure, and I’ve re-opened #8308
|  
|  Oh dear, it looks like I neglected to add the T11108.stdout to the
|  repository before push. Sorry about that.
|  
|  T8308 on the other hand I am quite perplexed by. This test passes for
|  me. Can you provide the output of,
|  
|      make test TEST=T8308
|  
|  Cheers,
|  
|  - Ben



More information about the ghc-devs mailing list