On Fri, Jul 21, 2023 at 05:57:23AM -0500, G. Branden Robinson wrote: > But I see no mechanism for interacting with autopkgtests to force them > to re-run due to the remedy of a defect in the test harness itself. > > How is this to be done? Should some automated mechanism for achieving > this be added, and if so, where?
You already found the retry button from previous replies, but you don't have to click it to get what you want… See how migrating groff/1.23.0-2 to testing was tested (and failed) every day without you lifting a finger? https://ci.debian.net/packages/d/dgit/testing/amd64/ Triggering a rerun now would be pointless as (a fixed) dgit needs to migrate first before groff can… which should be around ~tomorrow. After all, groff can only migrate if importing it into testing isn't causing a regression and it does as long as a bad dgit is in testing. I guess the day after ~tomorrow groff will migrate as well – assuming dgit was really your only problem. Best regards David Kalnischkies
signature.asc
Description: PGP signature
