Bug 29500 - Some tests failed due to timeout on RISCV64 real hardware
Summary: Some tests failed due to timeout on RISCV64 real hardware
Alias: None
Product: glibc
Classification: Unclassified
Component: build (show other bugs)
Version: 2.36
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
Depends on:
Reported: 2022-08-17 08:02 UTC by Letu Ren
Modified: 2022-08-17 09:20 UTC (History)
1 user (show)

See Also:
Last reconfirmed:


Note You need to log in before you can comment on or make changes to this bug.
Description Letu Ren 2022-08-17 08:02:23 UTC
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.
Comment 1 Andreas Schwab 2022-08-17 08:33:37 UTC
Set --with-timeoutfactor as appropriate.
Comment 2 Letu Ren 2022-08-17 09:07:04 UTC

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?
Comment 3 Andreas Schwab 2022-08-17 09:20:19 UTC
Run the affected tests with increasing values for TIMEOUTFACTOR until they succeed in time.