Sean Whitton writes ("Re: dgit in stretch-backports"):
> I prepared the backport earlier today but in a stretch chroot the test
> suite has two failures:
>
> gdr-newupstream FAIL non-zero exit status 16
> gdr-viagit FAIL non-zero exit status 16
>
> Ian, could you take a look at the log, please?
>
> I think these are just another gnupg failure that need not delay the
> backport, but it would be good to get your opinion on it.
I think this is something else. I always run the tests on stretch
during development so I don't think there is anything fundamentally
wrong, but the behaviour is certainly odd and does not look like the
usual gnupg2 race bugs. Looking at the error message, line 21
gpg-locked is (roughly)
$DGIT_TEST_REAL_GPG --agent-program=$DGIT_STUNT_AGENT
and this suggests that DGIT_TEST_REAL_GPG is not set. So I think the
most likely explanation is a bug in the test suite. Of course that
means that these tests were not run.
I will see if I can repro it in adt with a stretch chroot.
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
