** Description changed: - As it tries to calibrate how many samples will take more than 5 seconds - to execute, it may end up picking up a number of samples that take 10 - (but up to 12) seconds. As the calibration will take double that time, - it takes around 20 seconds. Then, it executes the whole thing again, and - then once more, with some added overhead. So, the thing might take more - than 40 seconds, which is too close to the 45s timeout. + [Impact] + seccomp selftests will timeout, causing the test to be detected as failure. + + [Fix] + Set timeout to 90s. + + [Test case] + Run sudo make run_tests under tools/testing/selftests/seccomp/. + + [Regression potential] + Minimal, the test could still timeout, but by reading the code, it should take around 42s to 50s to execute in the worst cases, so 90s seem safe enough. + + ====================================== + + + As it tries to calibrate how many samples will take more than 5 seconds to execute, it may end up picking up a number of samples that take 10 (but up to 12) seconds. As the calibration will take double that time, it takes around 20 seconds. Then, it executes the whole thing again, and then once more, with some added overhead. So, the thing might take more than 40 seconds, which is too close to the 45s timeout. So, it times out once in a while depending on the system. Using a timeout of 90 seconds should be safe enough for this test.
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881576 Title: seccomp_benchmark times out on eoan Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: In Progress Bug description: [Impact] seccomp selftests will timeout, causing the test to be detected as failure. [Fix] Set timeout to 90s. [Test case] Run sudo make run_tests under tools/testing/selftests/seccomp/. [Regression potential] Minimal, the test could still timeout, but by reading the code, it should take around 42s to 50s to execute in the worst cases, so 90s seem safe enough. ====================================== As it tries to calibrate how many samples will take more than 5 seconds to execute, it may end up picking up a number of samples that take 10 (but up to 12) seconds. As the calibration will take double that time, it takes around 20 seconds. Then, it executes the whole thing again, and then once more, with some added overhead. So, the thing might take more than 40 seconds, which is too close to the 45s timeout. So, it times out once in a while depending on the system. Using a timeout of 90 seconds should be safe enough for this test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1881576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
