On Sun 2017-11-12 17:59:47 +0100, Kurt Roeckx wrote: > On Mon, Nov 13, 2017 at 12:09:05AM +0800, Daniel Kahn Gillmor wrote: >> On Sun 2017-11-12 15:45:26 +0100, Ondřej Surý wrote: >> > Control: forwarded -1 >> > https://gitlab.labs.nic.cz/knot/knot-resolver/issues/272 >> > >> > dkg, I told you :) >> >> I don't think this is the same problem. knot-resolver 1.5.0-1 already >> patches around the upstream problem Ondřej points to with: >> >> >> https://anonscm.debian.org/git/pkg-dns/knot-resolver.git/tree/debian/patches/0002-work-around-https-gitlab.labs.nic.cz-knot-knot-resol.patch >> >> It builds cleanly on my own amd64 cowbuilder instance. I think this >> should be a giveback for the amd64 buildd network, to see if it repeats. > > Given back.
ok, it failed again on x86-csail-01 (same buildd as the first failure). So it's probably not a transient failure on that machine. is there a way to see whether some other amd64 build daemon can take it back? The package builds fine on the other architectures, though. I've just pushed 1.5.0-3, which hopefully contains a much more verbose attempt to run the test that appears to be failing, maybe we can see where it aborts on x86-csail-01. --dkg
signature.asc
Description: PGP signature
