setsockopt06 and writev03 from ubuntu_ltp_syscalls timeout on N/O

[Po-Hsu Lin]

While testing the LTP update with HEAD set to 20e346e7380 "testcases: add module signature enforcement check".

The setsockopt06 and writev03 test from ubuntu_ltp_syscalls will timeout with this version:
     START ubuntu_ltp_syscalls.setsockopt06 ubuntu_ltp_syscalls.setsockopt06 timeout=900 timestamp=1736237685 localtime=Jan 07 08:14:45
 Persistent state client._record_indent now set to 2
 Persistent state client.unexpected_reboot now set to ('ubuntu_ltp_syscalls.setsockopt06', 'ubuntu_ltp_syscalls.setsockopt06')
 Waiting for pid 176409 for 900 seconds
 System python is too old, crash handling disabled
 Timer expired (900 sec.), nuking pid 176409
         ERROR ubuntu_ltp_syscalls.setsockopt06 ubuntu_ltp_syscalls.setsockopt06 timestamp=1736238585 localtime=Jan 07 08:29:45 Test timeout expired, rc=15

     START ubuntu_ltp_syscalls.writev03 ubuntu_ltp_syscalls.writev03 timeout=900 timestamp=1736239160 localtime=Jan 07 08:39:20
 Persistent state client._record_indent now set to 2
 Persistent state client.unexpected_reboot now set to ('ubuntu_ltp_syscalls.writev03', 'ubuntu_ltp_syscalls.writev03')
 Waiting for pid 194535 for 900 seconds
 System python is too old, crash handling disabled
 Timer expired (900 sec.), nuking pid 194535
         ERROR ubuntu_ltp_syscalls.writev03 ubuntu_ltp_syscalls.writev03 timestamp=1736240060 localtime=Jan 07 08:54:20 Test timeout expired, rc=15

Bisect indicates this might be the cause:
2da30df24 lib: multiply the max_runtime if detect slow kconfigs

And we do have CONFIG_LATENCYTOP defined in our kernel.

[Po-Hsu Lin (cypressyew)]

Interesting finding is if you run these two tests directly, they will pass without any issue.
So it appears this is the autotest timeout kicks in.

[Po-Hsu Lin (cypressyew)]

A manual test shows it will take about 44 minutes to run through all these 2 tests.

And here is the output with autotest timeout bumped to 30 minutes:
10:50:34 ERROR| [stderr] real 18m0.401s
10:50:34 ERROR| [stderr] user 21m10.697s
10:50:34 ERROR| [stderr] sys 0m0.618s
10:50:36 INFO | GOOD ubuntu_ltp_syscalls.setsockopt06

11:16:01 ERROR| [stderr] real 25m25.136s
11:16:01 ERROR| [stderr] user 16m43.140s
11:16:01 ERROR| [stderr] sys 19m4.649s
11:16:02 INFO | GOOD ubuntu_ltp_syscalls.writev03

[Po-Hsu Lin (cypressyew)]

So yes, I can confirm commit 2da30df24 is the cause.
Removing the CONFIG_LATENCYTOP check from lib/tst_kconfig.c can make it pass like before.

It feels like this is simply extending the test execution time.

To make it pass, the timeout threshold must be set to 20 mins for setsockopt06, and 30 for writev03 in autotest-client-tests.

[Po-Hsu Lin (cypressyew)]

I think this test issue can be fixed by https://github.com/linux-test-project/ltp/commit/893ca0abe7e82851ff0e5d93c09b1098f2eff121