[Buildbot-devel] Buildbot-0.7.12rc2

[Dustin J. Mitchell]

On Mon, Jan 11, 2010 at 5:37 AM, Axel Hecht <l10n.moz at googlemail.com> wrote:
> I don't think it's testNoMerges, tbh. The test alone runs fine, even though
> I'm able to reproduce the failure if running the whole test suite. It
> complains about the reactor not being empty, so I blame a previous test for
> not cleaning up. My uneducated guess would be test_maildir, though I have no
> clue why, that test didn't change at all.
>
> trial doesn't let me run a subset of tests in order, so it's hard to figure
> out which combination of test cases actually triggers it.

FWIW, we've been chasing this and related errors for a while now.
After some talk in #buildbot, my new opinion on the matter is that
tests that fail for unknown reasons are bad tests, and should be
deleted.  If that means we end up with untested code, that's better
than having tests that we expect to fail "sometimes".

I know, it ain't ideal, and it's particularly non-ideal for an
application that is *part* of the software-testing apparatus, but it's
the best I can do.

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com