[Piuparts-devel] Failing at understanding piuparts log

[Nicolas Dandrimont]

* David Lamparter <equinox-debian at diac24.net> [2020-01-17 17:46:36 +0100]:

> On Fri, Jan 17, 2020 at 04:58:00PM +0100, Nicolas Dandrimont wrote:
> > * David Lamparter <equinox-debian at diac24.net> [2020-01-10 06:50:02 +0100]:
> > > https://piuparts.debian.org/stable2sid/fail/libyang0.16_0.16.105-2.log
> > 
> > This is a false-positive, which has been caused by a bug introduced when
> > piuparts was ported to Python3 (and that port was deployed on Dec 28th).
> 
> Ah, dang, Thanks.  Bad luck on my timing :)
> 
> > We had quite the backlog of failures to go through, but I think that
> > libyang0.16 has been retested since then, and that test was successful.
> 
> If it has rerun, the log isn't up ("Start: 2019-12-28 17:21:59 GMT",
> note this is "stable2sid" not "sid") but I need to roll a -3 anyway due
> to MIPS breakage so I'll just look at that.

Hey,

I have a pass log here on the backend (dated Jan 15th), but I guess the web
bits haven't updated properly. Now I get to figure out why :D

I'll probably have some time to look into that over the weekend.

Cheers,
-- 
Nicolas Dandrimont

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/piuparts-devel/attachments/20200117/788af9d9/attachment.sig>