When disabling tests during a release, I highly recommend documenting the disabled tests in a 'known bugs' file. Users should be told if we expect things not to work. It might also inspire someone to provide fixes :O)
Cheers, TAA -------------------------------------------------- Tony Abou-Assaleh Ph.D. Candidate, Faculty of Computer Science Dalhousie University, Halifax, NS, Canada, B3H 1W5 Fax: 902-492-1517 Email: [EMAIL PROTECTED] WWW: http://www.cs.dal.ca/~taa/ ---------------------[THE END]-------------------- On Thu, 28 Apr 2005, Julian Foad wrote: > (Redirected to the mailing list.) > > Gordon Lack wrote: > > Do you know the current CVS build fails 11 tests? (Not sure if this > > is a "normal" state). > > Yes, this is intentional. These are current bugs for which we are awaiting > fixes. (Some of the fixes may be in the patch queue.) We wouldn't wan't to > release a version with tests that fail, so if we want to release before fixing > them all we would disable the tests that fail. Ideally these tests would be > in > "expected failure" mode, but our test suite doesn't yet have that mode. > > - Julian > >
