The riscv64 build still fails with a test timeout of 30m. Since there
appears to be quite a substantial difference in performance between a
riscv64 porterbox, and the actual riscv64 buildd, I think we have no
option other than to skip the test completely.
=== RUN TestTombstoneCleanRetentionL
For the record, the following test also just timed out on i386:
=== RUN TestRulesUnitTest/Long_evaluation_interval
Unit Testing: ./testdata/long-period.yml
panic: test timed out after 20m0s
So perhaps we need to increase the baseline test timeout for _all_ archs
to at least e.g. 30 mins.
60 minutes is a big jump up from 20 minutes, especially if the test
duration is only just on the border of the current 20 minute timeout. I
would suggest a slightly more conservative increase, e.g. 30 minutes, so
as not to unnecessarily tie up the s390x hosts if some test has
terminally blocked
Source: prometheus
Version: 2.39.1+ds1-2
Severity: wishlist
Tags: ftbfs patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: m...@debian.org, debian-ri...@lists.debian.org
Hello,
This package fails frequently in most of the build machines of this architecture
due to timeouts,
4 matches
Mail list logo
