From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Li Wang" <li.wang@linux.dev>
Cc: Xuewen Wang <wangxuewen@kylinos.cn>,
ltp@lists.linux.it, linuxtestproject.agent@gmail.com
Subject: Re: [LTP] memcg/functional: fix memcg_failcnt intermittent timeout by disabling swap
Date: Fri, 07 Aug 2026 05:34:49 +0000 [thread overview]
Message-ID: <6a756e7a.cc089686.309364.c33e@mx.google.com> (raw)
In-Reply-To: <anVWjUOj6Oi5sBbz@linux.dev>
Hi Li,
> Fair point that ignoring the return status defeats the purpose. But I'd
> rather not TBROK on a swapoff failure, that's an environment limitation,
> not a test failure. Especially swapoff here is an enhancement but not
> a hard requirement for this test.
I agree.
> That is a bit over-engineering.
>
> If an inactive fstab entry gets activated by swapon -a, that arguably
> points to a misconfigured test host rather than something this test
> should work around.
And also here. Unfortunately we don't have enough data for shell tests,
so AI agent is not really working well in there..
Honestly I don't know how to fix this but adding more examples which
we don't have..
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-08-07 5:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 1:44 [LTP] [PATCH v3] memcg/functional: fix memcg_failcnt intermittent timeout by disabling swap Xuewen Wang
2026-08-07 2:51 ` [LTP] " linuxtestproject.agent
2026-08-07 3:52 ` Li Wang
2026-08-07 5:34 ` Andrea Cervesato via ltp [this message]
2026-08-07 6:20 ` Li Wang
2026-08-07 3:28 ` [LTP] [PATCH v3] " Li Wang
-- strict thread matches above, loose matches on Subject: below --
2026-08-05 6:40 [LTP] [PATCH v2] " Xuewen Wang
2026-08-05 7:40 ` [LTP] " linuxtestproject.agent
2026-07-31 1:49 [LTP] [PATCH] " Xuewen Wang
2026-07-31 2:46 ` [LTP] " linuxtestproject.agent
2026-08-03 13:38 ` Andrea Cervesato via ltp
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=6a756e7a.cc089686.309364.c33e@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=li.wang@linux.dev \
--cc=linuxtestproject.agent@gmail.com \
--cc=wangxuewen@kylinos.cn \
/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