[Devel] [PATCH vz10 3/3] selftests: kvm: raise the timeout the suite gives each test

[Eva Kurchatova <eva.kurchatova@virtuozzo.com>]

kvm/settings asks for 120 seconds per test, which mmu_stress_test cannot
meet on any machine. It writes a 128gb guest address space by default,
and the size is settable only on the command line, which the kselftest
runner does not pass:

  not ok 1 selftests: kvm: mmu_stress_test # TIMEOUT 300 seconds

It is not stuck, it is long, and how long depends on how many vCPUs it
gets, which is 3/4 of the cpus of the machine. Measured to completion,
all passing:

  40 cpus, 30 vCPUs    171s
   4 cpus,  3 vCPUs    436s
   2 cpus,  1 vCPU    1094s

Ask for 1800 seconds, which leaves room above the slowest of those for a
machine that is also busy. The cost is that the limit applies to every
test in the suite, so a test that really does hang now takes that long
to be killed; nothing else in the suite runs for more than a few tens of
seconds today.

A timeout given on the runner command line replaces this value
entirely, so it has to be at least as large.

https://virtuozzo.atlassian.net/browse/VSTOR-139672
Feature: fix vz selftests
Signed-off-by: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
---
 tools/testing/selftests/kvm/settings | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/testing/selftests/kvm/settings b/tools/testing/selftests/kvm/settings
index 6091b45d226b..abc5648b59ab 100644
--- a/tools/testing/selftests/kvm/settings
+++ b/tools/testing/selftests/kvm/settings
@@ -1 +1 @@
-timeout=120
+timeout=1800
-- 
2.55.0

_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel