From: kernel test robot <oliver.sang@intel.com>
To: Yosry Ahmed <yosryahmed@google.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
"David Hildenbrand" <david@redhat.com>, <oliver.sang@intel.com>
Subject: [linux-next:master] [mm] 5d4a36365b: kernel-selftests.cgroup.test_kmem.test_kmem_memcg_deletion.fail
Date: Wed, 12 Jun 2024 12:49:39 +0800 [thread overview]
Message-ID: <202406121026.579593f2-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "kernel-selftests.cgroup.test_kmem.test_kmem_memcg_deletion.fail" on:
commit: 5d4a36365be0fc9085c192b0015b789ddfaca1f8 ("mm: rmap: abstract updating per-node and per-memcg stats")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master d35b2284e966c0bef3e2182a5c5ea02177dd32e4]
in testcase: kernel-selftests
version: kernel-selftests-x86_64-977d51cf-1_20240508
with following parameters:
group: cgroup
compiler: gcc-13
test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz (Ivy Bridge) with 16G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
bc80784601ad8fd8 5d4a36365be0fc9085c192b0015
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:6 100% 6:6 kernel-selftests.cgroup.test_kmem.test_kmem_memcg_deletion.fail
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/202406121026.579593f2-oliver.sang@intel.com
# timeout set to 300
# selftests: cgroup: test_kmem
# not ok 1 test_kmem_basic
# memory.current = 331776
# anon + file + kernel + sock = 34463744
# anon = 34406400
# file = 0
# kernel = 57344
# sock = 0
# not ok 2 test_kmem_memcg_deletion <-----
# ok 3 test_kmem_proc_kpagecgroup
# ok 4 test_kmem_kernel_stacks
# ok 5 test_kmem_dead_cgroups
# memory.current 20328448
# percpu 13920000
# not ok 6 test_percpu_basic
not ok 2 selftests: cgroup: test_kmem # exit=1
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240612/202406121026.579593f2-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-06-12 4:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 4:49 kernel test robot [this message]
2024-06-12 6:54 ` Yosry Ahmed
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=202406121026.579593f2-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=yosryahmed@google.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