mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vishal Chourasia <vishalc@linux.ibm.com>
To: tj@kernel.org, hannes@cmpxchg.org, mkoutny@suse.com
Cc: cgroups@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Vishal Chourasia <vishalc@linux.ibm.com>
Subject: [PATCH] selftests/cgroup: add settings file with a longer timeout
Date: Tue, 29 Sep 2026 01:30:34 +0530	[thread overview]
Message-ID: <20260928200034.1769120-1-vishalc@linux.ibm.com> (raw)

The cgroup selftests lack a settings file, causing the kselftest runner
to apply its default 45s timeout. The test_cpu binary now exceeds this
limit, resulting in timeout failures that prevent the final test cases
from reporting results:

  not ok 2 selftests: cgroup: test_cpu # TIMEOUT 45 seconds

Test execution times:
|Test                  | Duration             |
|----------------------|--------------------  |
|cpu.weight (×4)       | ~10s each            |
|test_cpucg_stats      |  2s CPU time         |
|test_cpucg_nice       |  2s CPU time         |
|test_cpucg_max        |  1000/HZ seconds     |
|test_cpucg_max_nested |  1000/HZ seconds     |

Total runtime: ~46s at HZ=1000, ~64s at HZ=100

When executed independently, all nine test cases complete
successfully (46.2s on a ppc64le HZ=1000 guest).

Introduce a settings file that increases the timeout to 120 seconds,
providing sufficient margin above the HZ=100 worst-case scenario.

Signed-off-by: Vishal Chourasia <vishalc@linux.ibm.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..6091b45d226b
--- /dev/null
+++ b/tools/testing/selftests/cgroup/settings
@@ -0,0 +1 @@
+timeout=120
-- 
2.54.0


             reply	other threads:[~2026-09-28 20:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28 20:00 Vishal Chourasia [this message]
2026-09-28 20:17 ` Tejun Heo

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=20260928200034.1769120-1-vishalc@linux.ibm.com \
    --to=vishalc@linux.ibm.com \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mkoutny@suse.com \
    --cc=tj@kernel.org \
    /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

all inboxes | Powered by JetHome®