On 12/28/21 21:40, Bas Couwenberg wrote:
The upload of proj (8.2.1~rc1-1~exp1) to experimental resulted in an
autopkgtest regression on amd64:
https://release.debian.org/britney/pseudo-excuses-experimental.html#proj
The logs shows a couple of errors:
[...]
https://ci.debian.net/data/autopkgtest/unstable/amd64/g/gnudatalanguage/17896075/log.gz
The test_tic_toc issue seems to have already been reported in #1002584.
The upload of proj (8.2.1-1) to unstable did not trigger an autopkgtest
regression:
https://release.debian.org/britney/update_excuses.html#proj
Perhaps the autopkgtest of gnudatalanguage should be marked as flaky:
flaky
The test is expected to fail intermittently, and is not suitable for
gating continuous integration. This indicates a bug in either the
package under test, a dependency or the test itself, but such bugs
can be difficult to fix, and it is often difficult to know when the
bug has been fixed without running the test for a while. If a
``flaky`` test succeeds, it will be treated like any other
successful test, but if it fails it will be treated as though it
had been skipped.
https://salsa.debian.org/ci-team/autopkgtest/raw/master/doc/README.package-tests.rst
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
