*** This bug is a duplicate of bug 1939016 ***
https://bugs.launchpad.net/bugs/1939016
** This bug has been marked a duplicate of bug 1939016
ubuntu_ltp_syscalls:clock_settime03: failed with timeout
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/1980085
Title:
ubuntu_ltp_syscalls:clock_settime03: timeout with J-OEM-5.17
Status in ubuntu-kernel-tests:
New
Bug description:
Issue found on Jammy 5.17.0-1012-oem with node vought
Test timeout with the default 5 min setting.
However, even with timeout bumped to 50 minutes this issue is still
there:
<<<test_start>>>
tag=clock_settime03 stime=1656413592
cmdline="clock_settime03"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
tst_test.c:1456: TINFO: Timeout per run is 0h 50m 00s
clock_settime03.c:35: TINFO: Testing variant: syscall with old kernel spec
Test timeouted, sending SIGKILL!
tst_test.c:1506: TINFO: If you are running on slow machine, try exporting
LTP_TIMEOUT_MUL > 1
tst_test.c:1508: TBROK: Test killed! (timeout?)
Summary:
passed 0
failed 0
broken 1
skipped 0
warnings 0
<<<execution_status>>>
This is not a regression, this issue can be found with:
* J-oem 5.17.0-1009.9 node vought
* J-oem 5.17.0-1005.5 node vought
* J-oem 5.17.0-1004.4 node spitfire
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1980085/+subscriptions
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help : https://help.launchpad.net/ListHelp
