> We don't have a tradition of accepting tests that fail, but it might be a > good idea to consider accepting such tests into unstable, and maybe even > into the stable repository, if the test reveals a regression that we > *really* want fixed in a timely manner. Although it is sort of scary > having any repository that doesn't pass its own tests...
For the moment, I don't accept these in the repo (although I do welcome them and mention them in my Waiting for Code summaries). My thinking is that [i] the pref that forces a test when you record is probably a good thing (you can also use --no-test) [ii] if we want to have that test, we must make sure our own tests pass so that people submitting patches know for sure if test failing is their doing or not. I basically don't want to scare anybody off from submitting a patch because 'Looks like a bad patch to me!' Am willing to rethink this, of course. -- Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon français.
pgp3lTNprJLe2.pgp
Description: PGP signature
_______________________________________________ darcs-devel mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-devel
