Hi,

On 02-05-2022 02:39, Debian Bug Tracking System wrote:
  macaulay2 (1.19.1+ds-9) unstable; urgency=medium
  .
    * debian/tests/control
      - Mark package-tests as flaky since it regularly times out on armhf
        (Closes: #1010453).

Hmmm. May I recommend something else?

Marking autopkgtests that regularly time out is a solution that has a relative high price on the infrastructure. These tests are still run (until they time out), while they don't influencing migration of any package if the package contain more than one autopkgtest. Marking tests flaky is nearly only useful if a human is regularly going to look at the results and does something with it. To be honest, I'm not expecting that here (but let me know if I'm making a wrong assumption here).

Instead, I recommend to not run the test at all on armhf if we're going to ignore the result there (successful runs also take long), but use it normally on all other architectures. There's the "Architecture" field available in debian/tests/control that can be used to achieve that in a correct way. It understands the regular syntax so "!armhf" should suffice.

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to