Hi, I'm building glibc on ArchLinux RISCV64 with a unmatched board. Some tests failed due to timeout. As SiFive unmatched board is high performance, I think testsuite shouldn't time out on it. According to the release notes of glibc 2.36, only four tests failed. I wonder what hardware do developers use. I'll list failing tests below. I can also list time consumed if needed. FAIL: locale/tst-localedef-path-norm FAIL: malloc/tst-malloc-too-large-malloc-hugetlb2 FAIL: nptl/tst-mutex10 FAIL: nss/tst-nss-files-hosts-getent FAIL: nss/tst-nss-files-hosts-multi FAIL: stdio-common/tst-vfprintf-width-prec FAIL: stdlib/test-bz22786 FAIL: stdlib/tst-arc4random-fork FAIL: string/test-memcpy FAIL: string/test-mempcpy FAIL: string/test-strncasecmp FYI, my environment are Linux 5.18.3, gcc 12.1.1 20220730 and binutils 2.39.
Set --with-timeoutfactor as appropriate.
Hi, What is the appropriate argument of --with-timeoutfactor? Could you suggest one or should I try to find one myself? The aim of our project is to bridge the gap of ArchLinux build system between x86_64 and RISCV64. So, is it possible to change the default timeout value?
Run the affected tests with increasing values for TIMEOUTFACTOR until they succeed in time.