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
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
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
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
Hi folks,
Regarding:
https://tracker.debian.org/pkg/groff
...progress of groff into testing is blocked because autopkgtests went
bonkers, failing on every architecture. This was due to a change in a
groff diagnostic message not getting scraped away by dgit, which was
using a regex to match the
5 matches
Mail list logo
