Re: How do you cause a re-run of autopkgtests?
Hi, On 21-07-2023 14:20, David Kalnischkies wrote: 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… The migration software of the release team retries failures after 24 hours. Configuration specifying the retry age lives here: [1]. Paul [1] https://salsa.debian.org/release-team/britney2/-/blob/master/etc/britney.conf#L103 OpenPGP_signature Description: OpenPGP digital signature
Re: How do you cause a re-run of autopkgtests?
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
Re: How do you cause a re-run of autopkgtests?
At 2023-07-21T13:43:05+0200, IOhannes m zmölnig (Debian/GNU) wrote: > On 7/21/23 12:57, G. Branden Robinson wrote: > > Hi folks, > > > > 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? > > you mean, apart from clicking on the ♻ retry icon? Oh, _that's_ what that means! It had no tooltip, but if I peer at the URL preview it does say "retry", so I must confess blindness as well as ignorance. > (you probably have to be authenticated in order to even see these > icons) I don't have to be authed to _see_ it, but if I click on it, a login is demanded of me. Fair enough (robot/DoS defense). > > Should some automated mechanism for achieving this be added, and if > > so, where? > > https://ci.debian.net/api/doc As a bear of little brain, I can indeed infer from this that a mechanism for prompting retry exists. Thanks for the pointers! Regards, Branden signature.asc Description: PGP signature
Re: How do you cause a re-run of autopkgtests?
On 7/21/23 12:57, G. Branden Robinson wrote: Hi folks, 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? you mean, apart from clicking on the ♻ retry icon? (you probably have to be authenticated in order to even see these icons) Should some automated mechanism for achieving this be added, and if so, where? https://ci.debian.net/api/doc mgfdsar IOhannes
