Paul Gevers writes ("Re: Bug#901897 closed by Jonathan Nieder
<jrnie...@gmail.com> (Bug#901897: fixed in git 1:2.18.0~rc2-2)"):
> And I just helped the test for git a bit as due to bug 896023 in
> autopkgtest it didn't use the right autopkgtest from dgit.
Thanks.
It's not clear to me exactly what needed fixing. Can you send me urls
to the bad run which prompted your intervention, and the good run
which resulted ?
Looking here
https://qa.debian.org/excuses.php?package=git
I see a migration test for git 1:2.18.0-1 which used dgit 5.1,
despite the fact that dgit 5.1 is not in testing yet.
But that is appropriate, because the new git Breaks earlier versions
of dgit. AIUI britney will therefore not migrate the new git until
the new dgit is migrated, which is correct.
Looking at the test log[1] it used the test suite from 5.1, too.
I don't know how other packages do things, but in general, with dgit
at least, mixing and matching program versions and test versions may
work some of the time: particularly, newer programs will usually pass
older tests. Older programs will typically fail newer tests since the
newer tests will look for new features.
In this particular case: dgit 4.4's test suite will always fail with
the new git. dgit 5.1's test suite will properly test whether the
tested dgit and git are compatible: so it will only fail with new git
and old dgit.pass with old git; and with new git:
git dgit test suite dgit result
1:2.17.1-1 4.4, 5.0, 5.1 4.4, 5.0, 5.1 PASS
1:2.18.0-1 <= 5.0 any FAIL
1:2.18.0-1 5.1 <= 5.0 FAIL
1:2.18.0-1 5.1 5.1 PASS
AFAICT from the migration information from britney from yesterday and
today, all is fine except for git's an artificially inflated urgency.
Ian.
[1] https://ci.debian.net/data/autopkgtest/testing/amd64/d/dgit/491815/log.gz
--
Ian Jackson <ijack...@chiark.greenend.org.uk> 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.
