remove failures when we request the failure to run and it doesn't
Bug #532407 reported by
Robert Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Testrepository |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
If testr explicit requests a test case X to run, and it doesn't, and the
stream generator does not error, then X has been deleted and the failure
info for it has become obsolete.
affects testrepository
status triaged
importance wishlist
done
To post a comment you must log in.
On Thu, 2010-03-04 at 23:28 +0000, Robert Collins wrote:
> Public bug reported:
>
> If testr explicit requests a test case X to run, and it doesn't, and the
> stream generator does not error, then X has been deleted and the failure
> info for it has become obsolete.
This may need more smarts than this - gtester stops running tests when
the first failure occurs, and other things may do that to. Perhaps a
config switch.
-Rob