On Mon, Sep 29, 2008 at 10:54:26 -0600, zooko wrote: > > Indeed, and they are run with 'make bugs'. We used to run them when > > make test (or equivalently make check) was run, but people seemed to > > get confused by that, so we removed them from the default check. > > It'd be helpful to be able to see which ones are still failing, so we > > could know when the bugs are fixed. Or on which platforms a given > > bug is present. > > Hm. The way that this is done with typical test software is to mark > individual tests, or groups of tests as "known to fail", and then the > test software doesn't raise an alarm if a test which is so flagged > fails, but it does raise a nice signal saying "Hey, unexpected > success!" when it succeeds.
If anybody wants to work on this, I think the tests/shell_harness script could be made smarter. There already is some logic in there, for example, to print the list of unexpected passes. All we need to do is to change the 'TESTS FAILED' output accordingly -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
signature.asc
Description: Digital signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
