From: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
To: khorenko@virtuozzo.com
Cc: devel@openvz.org
Subject: [Devel] [PATCH vz10 2/2] selftests: cgroup: add a settings file with a longer timeout
Date: Tue, 1 Sep 2026 02:36:55 +0300 [thread overview]
Message-ID: <20260831233703.1648144-2-eva.kurchatova@virtuozzo.com> (raw)
In-Reply-To: <20260831233703.1648144-1-eva.kurchatova@virtuozzo.com>
The cgroup tests ship no settings file, so the runner applies its
default of 45 seconds per test. test_memcontrol and test_zswap both
run longer than that and are killed mid-test:
not ok 1 selftests: cgroup: test_memcontrol # TIMEOUT 45 seconds
Add a settings file asking for 300 seconds. Upstream ships no settings
file for cgroup, and the value reflects the speed of the machine rather
than anything about the kernel, so it stays in this tree.
https://virtuozzo.atlassian.net/browse/VSTOR-139649
Feature: fix vz selftests
Signed-off-by: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
---
tools/testing/selftests/cgroup/settings | 1 +
1 file changed, 1 insertion(+)
create mode 100644 tools/testing/selftests/cgroup/settings
diff --git a/tools/testing/selftests/cgroup/settings b/tools/testing/selftests/cgroup/settings
new file mode 100644
index 000000000000..694d70710ff0
--- /dev/null
+++ b/tools/testing/selftests/cgroup/settings
@@ -0,0 +1 @@
+timeout=300
--
2.55.0
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next prev parent reply other threads:[~2026-08-31 23:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 23:36 [Devel] [PATCH vz10 1/2] ms/selftests/cgroup: skip test_zswap if zswap is globally disabled Eva Kurchatova
2026-08-31 23:36 ` Eva Kurchatova [this message]
2026-09-02 18:17 ` [Devel] [PATCH vz10 2/2] selftests: cgroup: add a settings file with a longer timeout Konstantin Khorenko
2026-09-02 18:17 ` [Devel] [PATCH vz10 1/2] ms/selftests/cgroup: skip test_zswap if zswap is globally disabled Konstantin Khorenko
2026-09-02 18:19 ` Konstantin Khorenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260831233703.1648144-2-eva.kurchatova@virtuozzo.com \
--to=eva.kurchatova@virtuozzo.com \
--cc=devel@openvz.org \
--cc=khorenko@virtuozzo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox