remove failures when we request the failure to run and it doesn't

Bug #532407 reported by Robert Collins on 2010-03-05
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Testrepository
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

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

Robert Collins (lifeless) wrote :

Trunk does most of this - when a full run happens, missing tests are removed. However on partial runs it does not cross reference the requested test id with the seen ones.

Changed in testrepository:
status: Triaged → Fix Committed
status: Fix Committed → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers