ubuntu_ltp sched:starvation fails with ARM64 on bos2 region

Bug #2059259 reported by Kevin Becker
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
New
Undecided
Unassigned

Bug Description

For the 2024.03.04 cycle and s2024.02.05 cycle, ubuntu_ltp sched:starvation failed on j/realtime on bos2 region. Switching it to bos1 region allowed it to pass during the s2024.02.05 cycle.

Examples of failure from 2024.03.04:

tst_test.c:1741: TINFO: LTP version: 20230929-407-g58aa31f55
tst_test.c:1625: TINFO: Timeout per run is 0h 00m 30s
starvation.c:57: TPASS: sched_setaffinity(0, sizeof(mask), &mask) returned 0
tst_test.c:1633: TINFO: Updating max runtime to 0h 04m 00s
tst_test.c:1625: TINFO: Timeout per run is 0h 04m 30s
Test timeouted, sending SIGKILL!
tst_test.c:1673: TINFO: Killed the leftover descendant processes
tst_test.c:1679: TINFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1
tst_test.c:1681: TBROK: Test killed! (timeout?)

Sean Feole (sfeole)
tags: added: 5.15 arm64 openstack realtime sru-20240304 ubuntu-ltp
description: updated
tags: added: sru-s20240205
Revision history for this message
Kevin Becker (kevinbecker) wrote :

Running the test on bos1 for the 2024.03.04 cycle made the test pass, similar to s2024.02.05.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

This issue can be found on F-5.15 64k as well.

Experiments with F-5.15.0-102-generic-64k shows it will take:
 * 4m37.231s
 * 4m32.198s
 * 4m32.442s
 * 4m33.488s
 * 4m34.977s
 * 4m33.371s
 * 4m33.577s
 * 4m32.672s
 * 4m34.560s
 * 4m37.162s
For this test to run on bos02. Just slightly above the 4m30s threshold.

Setting LTP_TIMEOUT_MUL=2 can bump the timeout to 5m00s and this test will pass.

Po-Hsu Lin (cypressyew)
summary: - ubuntu_ltp sched:starvation fails on bos2 region
+ ubuntu_ltp sched:starvation fails with ARM64 on bos2 region
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Experiments with J-5.15.0-1058-realtime on bos02 ARM64 shows it will take:
  * 5m4.261s
  * 5m8.267s
  * 5m9.418s
  * 5m11.923s
  * 5m4.715s
  * 5m17.411s
  * 5m11.225s
  * 5m7.947s
  * 5m16.900s
  * 5m28.553s

In this case we will need LTP_TIMEOUT_MUL=3 to bump the LTP timeout to 5m30s (or even set it to 4).
Thoughts?

BTW I have a hint added for F-5.15.0-102-generic-64k.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.