Spurious test failure in TestCaptureOops.test_two_oops_gives_two_detail
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Unassigned |
Bug Description
test_two_
I ran the following command repeatedly in my locate environment and saw 1/3 failures.
./bin/test -vvc --layer=
I discovered this after moving webapp to lp.services and got an error I could only reproduce by creating a similar test order.
I see that webapp tests are still played before the failing test (lp.services.webapp and lp.testing), I do not think the interaction problem is between webapp and testing, maybe this this webapp playing after other test?
=======
FAILURE: lp.testing.
-------
_StringException: Text attachment: traceback
------------
Traceback (most recent call last):
_StringException: oops-0: {{{
Oops-Id: OOPS-9fc00ba1b2ecd2e36ee745ce8b7c2a21
Exception-Type: AssertionError
Exception-Value: Exception to get a traceback.
Date: 2011-12-
Branch: test
Revision: 14602
Duration: -1
Oops-Reporter: T
Traceback (most recent call last):
Module lp.testing.
raise AssertionError(
AssertionError: Exception to get a traceback.
}}}
Traceback (most recent call last):
File "/var/launchpad
sorted([a for a in self.getDetails() if "oops" in a]))
AssertionError: ['oops-0', 'oops-1'] != ['oops-0']
tags: | added: build-infrastructure |