On 28/02/2011 11:39, Dimitrios Vytiniotis wrote:
Hi, when I am working on a typechecker patch and then run the testsuite,
sometimes I get dozens
of error reports that look like:
Unexpected failures:
FD2(normal)
FrozenErrorTests(normal)
... etc
It would be helpful for me to be able to quickly see in the same line,
(i) which directory the
test is in, (ii) the name of the 3^rd parameter of the corresponding
all.T entry, and (iii) the exit
status of ghc when running that test. Something like:
FD2 (normal) (should_compile/) (compile_fail) (ghc failed)
FrozenErrorTests (normal) (should_fail/) (compile_fail) (ghc failed)
For instance, these entries tell me that a program from should_compile/
which was supposed
to fail still fails, so the problem is likely to be a shuffling in error
messages. If I see an entry:
MyFile (normal) (should_compile/) (compile) (ghc failed)
then that’s probably very serious.
All tests deserve attention but this extra information would help me to
focus very fast on
errors that look more important first and also to navigate to these
files w/o searching my
buffer to see where the file is all the time, or what are its all.T
parameters.
Is this something people think is generally useful, or is it already
possible, or am I talking nonsense here?
I like it. But instead of "ghc failed" I would print the reason for
failure - e.g. "run.stderr mismatch", "timeout", "expected exit(0) but
saw 139" etc.
Nice small job for a Python hacker(!), any takers?
Cheers,
Simon
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
