Control: tag -1 pending Hello,
Bug #1093275 in autopkgtest reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ci-team/autopkgtest/-/commit/9e86d5a2d9c18064fad57d8dc80f6b07c8cd6107 ------------------------------------------------------------------------ tests: By default only exercise timeouts on known-fast architectures We test timeouts by making one part of a test use sleep(1) to block for a while, trying to guess a timeout *T* that will be long enough to accommodate initial test setup (up to that point), setting autopkgtest's timeout to a little more than *T*, and making sleep(1) sleep for considerably more than *T*. If all goes well, this means that everything before the targeted point runs (and we can confirm this by screen-scraping the log), and then the test times out (and we can check that autopkgtest responds correctly to that). However, choosing an appropriate value of *T* is difficult. If we make *T* too long, successfully running the autopkgtest test suite takes that much longer, even on an arbitrarily fast machine; this is undesirable because full coverage implies running the test suite several times with different backends, which can be extremely time-consuming already (see #1020699). Conversely, if we make *T* too short, we can hit test failures on slower machines like riscv64, with the test timing out before initial setup has finished, meaning autopkgtest will (correctly!) report the failure differently. In practice the timeouts we have chosen are all tuned for reasonably fast developer machines like x86, and the code under test is identical on any architecture, so skip these tests by default on architectures that are not known to be fast and reliable. Developers can set `AUTOPKGTEST_TEST_TIMEOUTS=1` to force these tests to run even on slower architectures, or `AUTOPKGTEST_TEST_TIMEOUTS=0` to force them to be skipped even on fast architectures. Signed-off-by: Simon McVittie <s...@debian.org> Closes: #1093275 ------------------------------------------------------------------------ (this message was generated automatically) -- Greetings https://bugs.debian.org/1093275
