Hi! On Fri, Dec 22, 2023 at 05:25:52PM +0800, Bo YU wrote: > Package: qbs > Version: 1.24.1+dfsg-2 > Severity: important > Tags: ftbfs patch > User: debian-riscv@lists.debian.org > Usertags: riscv64 > X-Debbugs-Cc: debian-riscv@lists.debian.org > > Dear Maintainer, > > qbs has ftbfs on riscv64 since 2.1.1-2(2023/08) on sid. The problem is > due to timeout on buildd machines for riscv64 now: > > [...] > > So we can see the timeout on tst_blackbox-qt suite mainly. But the > question is that failed test function cases are randomized. So I have > captured a few cases to temporarily skip over riscv64 buildd(holpe this > works). And I would like to suggest that we keep opening the reportbug > until we have more powerful buildd machines to close it as expected > it. I can build it on vf2 without any patch but it has not been tested > many times. > > So could you apply it on next upload or any ideas? I would prefer increasing the timeout to disabling the test. The blackbox tests start qbs in a subprocess and wait for it to finish in a reasonable time [1]. The value of testTimeoutInMsecs() can be configured by QBS_AUTOTEST_TIMEOUT environment variable, which specifies time in seconds and is 600 by default, which is 10 minutes. However, Qt test library has its own timeout: any test function call is interrupted in 5 minutes [2]. This can be configured by QTEST_FUNCTION_TIMEOUT variable, which is in milliseconds. It looks like this is the timeout that occurs in the log fragments you provided. Do you have any way to check if increasing QTEST_FUNCTION_TIMEOUT helps to get it built on slow riscv64 machines. And if yes, to what value it should be increased? [1]: https://sources.debian.org/src/qbs/2.1.2-2/tests/auto/blackbox/tst_blackboxbase.cpp/#L100 [2]: https://doc.qt.io/qt-6/qtest-overview.html#increasing-test-function-timeout -- Dmitry Shachnev
Attachment:
signature.asc
Description: PGP signature