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. -- 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/2059259 Title: ubuntu_ltp sched:starvation fails with ARM64 on bos2 region Status in ubuntu-kernel-tests: New 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?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2059259/+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
