[m-rev.] diff: eliminate redundant bootcheck output
Zoltan Somogyi
zoltan.somogyi at runbox.com
Thu Jan 22 02:17:00 AEDT 2015
This diff makes the output of bootcheck somewhat shorter,
but it is still too long; it is still too hard to find any problems.
I propose two further changes to how we do the tests.
First, I propose that each test should be executed by a shell script,
whose output is stored in a file, and that this file should be printed
in the output of bootcheck ONLY if the test fails. We already do
something like this, with output from program executions being stored
in testname.log files, but I propose moving all output from the test,
including the commands executed (by sh -x), and the output of the
Mercury and C compilers, in this not-shown-if-the-test-works file.
Second, to make the first change easier, to flatten out the test case
directories. This would involve replacing e.g. tests/hard_coded/typeclasses
with just tests/typeclasses. We considered this a long time ago, but
it cannot be done without losing development history with CVS, but
it should be possible to do with git.
Any opinions, pro or contra?
Zoltan.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Log.bootcheck_redundancies
Type: application/octet-stream
Size: 1543 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20150122/f89dbf3d/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DIFF.bootcheck_redundancies
Type: application/octet-stream
Size: 25572 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20150122/f89dbf3d/attachment-0001.obj>
More information about the reviews
mailing list