Package: autopkgtest
Version: 5.5
When a new version of the package under test enters the archive during a
test run, the tests towards the end of the run may use the binaries of
the new version, but debci lists it as a test of the old version.
If these tests fail because the new version contains a regression, this
gives a "fail" entry for the _old_ version, and hence the false
impression that the problem must be somewhere else.
Example: row 2018-09-20 11:04:29 of
https://ci.debian.net/packages/p/pymca/unstable/amd64/
(This is probably #909379 not a pymca regression, but this log isn't
proof it isn't)
Possibly related to #896023 / #902027, but those are about testing vs
unstable, while this is changes within a suite.
This is moderately unlikely, but not hugely so: for pymca (~15min of
tests and a big enough dependency chain that it gets tested ~2x/day),
~2% chance per upload.
I'd guess the best solution is to make this a tmpfail, as testing an
already-superseded version is probably a waste of resources.
