On Mon, Dec 05, 2022 at 05:06:30PM -0800, Steve Langasek wrote:
> > However, sometimes you might find --apt-pocket=proposed=... *not* used,
> > even when triggers appear to exist. I didn't get to the bottom of this.
> > Maybe it's something to do with magic fallback behaviour I've heard
> > mentioned (an automatic retry with different conditions?) but couldn't
> > find anything documented and didn't find any implementation for this.
> > For example, looking at [1], vorlon's test dated 2022-11-28 19:26:59 UTC
> > and my subsequent retest dated 2022-11-30 10:20:55 UTC were subsequently
> > identical, but looking at the logs, his one was called with
> > --apt-pocket=proposed with no pinning defined, whereas mine was. All I
> > did was hit the retry button against vorlon's test request and failure,
> > and mine got run differently! I'd appreciate someone explaining this to
> > me.
>
> This seems to simply be a bug in what autopkgtest.ubuntu.com considers a
> 'retry', in that it is not propagating the all-proposed=1 option.
I filed https://bugs.launchpad.net/auto-package-testing/+bug/1999163 for
this - thanks.
Robie
