cgroups.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Shashank Balaji <shashank.mahadasyam@sony.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
	linux-kernel@vger.kernel.org, "Tejun Heo" <tj@kernel.org>,
	"Michal Koutný" <mkoutny@suse.com>,
	cgroups@vger.kernel.org, oliver.sang@intel.com
Subject: [linus:master] [selftests/cgroup]  954bacce36: kernel-selftests.cgroup.test_cpu.test_cpucg_max.fail
Date: Thu, 7 Aug 2025 13:52:31 +0800	[thread overview]
Message-ID: <202508070722.46239e7c-lkp@intel.com> (raw)



Hello,


we noticed 954bacce36 is to address "cpu.max tests", however, we found below
two tests can pass on parent, but failed on 954bacce36.

dfe25fbaedfc2a07 954bacce36d976fe472090b5598
---------------- ---------------------------
       fail:runs  %reproduction    fail:runs
           |             |             |
           :6           100%          6:6     kernel-selftests.cgroup.test_cpu.test_cpucg_max.fail
           :6           100%          6:6     kernel-selftests.cgroup.test_cpu.test_cpucg_max_nested.fail


not sure if there are any necessary env setting? thanks


kernel test robot noticed "kernel-selftests.cgroup.test_cpu.test_cpucg_max.fail" on:

commit: 954bacce36d976fe472090b55987df66da00c49b ("selftests/cgroup: fix cpu.max tests")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master

[test failed on linux-next/master 84b92a499e7eca54ba1df6f6c6e01766025943f1]

in testcase: kernel-selftests
version: kernel-selftests-x86_64-ae388edd4a8f-1_20250729
with following parameters:

	group: cgroup



config: x86_64-rhel-9.4-kselftests
compiler: gcc-12
test machine: 4 threads 1 sockets Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz (Ivy Bridge) with 8G memory

(please refer to attached dmesg/kmsg for entire log/backtrace)


If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202508070722.46239e7c-lkp@intel.com



# timeout set to 300
# selftests: cgroup: test_cpu
# ok 1 test_cpucg_subtree_control
# ok 2 test_cpucg_stats
# ok 3 test_cpucg_nice
# not ok 4 test_cpucg_weight_overprovisioned
# ok 5 test_cpucg_weight_underprovisioned
# not ok 6 test_cpucg_nested_weight_overprovisioned
# ok 7 test_cpucg_nested_weight_underprovisioned
# not ok 8 test_cpucg_max
# not ok 9 test_cpucg_max_nested
not ok 2 selftests: cgroup: test_cpu # exit=1



The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250807/202508070722.46239e7c-lkp@intel.com



-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


             reply	other threads:[~2025-08-07  5:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-07  5:52 kernel test robot [this message]
2025-08-11 21:32 ` [linus:master] [selftests/cgroup] 954bacce36: kernel-selftests.cgroup.test_cpu.test_cpucg_max.fail Michal Koutný

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=202508070722.46239e7c-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=cgroups@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mkoutny@suse.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=shashank.mahadasyam@sony.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;
as well as URLs for NNTP newsgroup(s).