On 23/11/2019 20:35, Paul Gevers wrote:
Hi Rebecca,
On 23-11-2019 15:33, Rebecca N. Palmer wrote:
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-feather-format/3483361/log.gz
appears to have the opposite problem: it finds the new source (-3), but
as this had not yet been built, it used the old binary (-2).
The root cause here should be a mirror that is out-of-date, as britney
only schedules the tests when the build is done (so your statement isn't
correct).
The autopkgtest is timestamped 15:22, the amd64 build finish 15:47.
Maybe this test was triggered by something other than
python-feather-format itself?
It will be retried after one day and all should be fine.
It now is.
