Failing tests are not re-triggered when package with failures is re-uploaded

Bug #1512779 reported by Iain Lane on 2015-11-03
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
britney
Medium
Unassigned

Bug Description

Case which happened today.

 - gtk+3.0 was uploaded
 - this triggered a test run of gvfs, which failed
 - gvfs was uploaded to fix this failure
 - gtk+3.0's trigger of gvfs did not get updated

Given that we are trying to install as little as possible from -proposed, the
run for gvfs itself would not get the new gtk+3.0. We need to run gvfs's tests
with a trigger of gtk+3.0.

That is, for an upload of a package P, re-trigger all triggers which were for P
and which failed. Don't do this in the other way (pass -> fail), since a new
failure can't be the fault of P here.

Martin Pitt (pitti) on 2015-12-02
Changed in auto-package-testing:
status: New → Triaged
importance: Undecided → Medium
Martin Pitt (pitti) on 2016-01-26
affects: auto-package-testing → britney
tags: added: auto-package-testing
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers