On Mon, Aug 28, 2006 at 10:14:24PM +0900, Charles Plessy wrote: > I am packaging a software which includes tests to check if the binary is > fully funcionnal. However, those tests are much more processor intensive > than the compilation itself. Is there a general policy about what to do
I don't know about a general policy, but I've myself set gecode to run its test suite in debian/rules, excluding some of the slower buildds. > with them? Is it enough to run them when testing the package before > upload, or should them be ran systematically by debian/rules, thus using > cpu power of the buildds? If you have tests, it's likely to be a good idea to run them on multiple architectures. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
