From: Kunwu Chan <kunwu.chan@linux.dev>
To: sj@kernel.org, shuah@kernel.org
Cc: damon@lists.linux.dev, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Kunwu Chan <kunwu.chan@gmail.com>
Subject: [PATCH 0/5] selftests/damon: misc fixes for test bugs
Date: Sun, 31 May 2026 16:56:28 +0800 [thread overview]
Message-ID: <20260531085633.48626-1-kunwu.chan@linux.dev> (raw)
From: Kunwu Chan <kunwu.chan@gmail.com>
This series fixes several bugs in the DAMON selftests. Most are
trivial but cause tests to silently pass when they shouldn't, or
fail prematurely on slow machines.
Patch 1 fixes mutable default arguments in DamonCtx.__init__()
that cause state to leak between test instances.
Patch 2 fixes a trailing comma in DamosFilter that turns
memcg_path from a string into a tuple, silently breaking memcg
filter setup.
Patch 3-4 fix bugs in damos_tried_regions.py: wrong operator
precedence drops the "not met" prefix from failure output, and
empty early aggregation cycles cause premature test failure.
Patch 5 fixes several wrong strings that produce dead elif
branches, skipped file existence checks, and broken dict key
lookups.
Based on next-20260529.
base-commit: 7da7f07112610a520567421dd2ffcb51beaefbcc
Kunwu Chan (5):
selftests/damon: prevent cross-context state pollution in DamonCtx
selftests/damon: fix memcg filter path handling
selftests/damon/damos_tried_regions: fix expectation output and join
TypeError
selftests/damon/damos_tried_regions: handle empty tried regions in
early cycles
selftests/damon: fix dead code, skipped checks, and broken lookups
tools/testing/selftests/damon/_damon_sysfs.py | 14 +++++++++----
.../selftests/damon/damos_apply_interval.py | 2 +-
.../selftests/damon/damos_quota_goal.py | 2 +-
.../selftests/damon/damos_tried_regions.py | 20 ++++++++++---------
.../selftests/damon/drgn_dump_damon_status.py | 2 +-
tools/testing/selftests/damon/sysfs.py | 4 ++--
tools/testing/selftests/damon/sysfs.sh | 6 +++---
...te_schemes_tried_regions_wss_estimation.py | 2 +-
8 files changed, 30 insertions(+), 22 deletions(-)
--
2.43.0
next reply other threads:[~2026-05-31 8:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 8:56 Kunwu Chan [this message]
2026-05-31 9:17 ` [PATCH 1/5] selftests/damon: prevent cross-context state pollution in DamonCtx Kunwu Chan
2026-05-31 9:17 ` [PATCH 2/5] selftests/damon: fix memcg filter path handling Kunwu Chan
2026-05-31 16:36 ` SeongJae Park
2026-06-01 2:19 ` Kunwu Chan
2026-05-31 9:17 ` [PATCH 3/5] selftests/damon/damos_tried_regions: fix expectation output and join TypeError Kunwu Chan
2026-05-31 16:39 ` SeongJae Park
2026-05-31 9:17 ` [PATCH 4/5] selftests/damon/damos_tried_regions: handle empty tried regions in early cycles Kunwu Chan
2026-05-31 16:54 ` SeongJae Park
2026-06-01 2:33 ` Kunwu Chan
2026-05-31 9:17 ` [PATCH 5/5] selftests/damon: fix dead code, skipped checks, and broken lookups Kunwu Chan
2026-05-31 16:59 ` SeongJae Park
2026-05-31 16:30 ` [PATCH 1/5] selftests/damon: prevent cross-context state pollution in DamonCtx SeongJae Park
2026-06-01 2:11 ` Kunwu Chan
2026-05-31 17:08 ` [PATCH 0/5] selftests/damon: misc fixes for test bugs SeongJae Park
2026-06-01 2:38 ` Kunwu Chan
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=20260531085633.48626-1-kunwu.chan@linux.dev \
--to=kunwu.chan@linux.dev \
--cc=damon@lists.linux.dev \
--cc=kunwu.chan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuah@kernel.org \
--cc=sj@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