Sean Whitton <spwhit...@spwhitton.name> writes: > I think we should move the tests to run under autopkgtest, rather than > during the build. Debian's autopkgtest infrastructure, with things like > blocking migration, is by now quite sophisticated. > > On IRC it's also been suggested that we also > > - mark dired-test-bug27243-02 as flaky (thanks Arto Jantunen); and > > - in the new autopkgtest, don't run the tests in parallel.
I don't have a good overall sense of what's been failing lately, but I did wonder if just marking that test (and any others that have been (unnecessary) trouble) as flaky, and going back to not running the tests in parallel on the autobuilders might be sufficient. As long as the package tests restrict transitions, moving the tests there, if we can, may be fine too, but if we could keep the spurious test failure rate low enough (pretty low) without *too* much effort, then I think catching failures during the build is somewhat preferable (in case the error is serious). Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
