From: linuxtestproject.agent@gmail.com
To: Piotr Kubaj <piotr.kubaj@intel.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] pmc_core: add test for pkgc_blocker_residency_show
Date: Thu, 13 Aug 2026 10:11:40 +0000 [thread overview]
Message-ID: <20260813101140.9156-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260813094549.196724-2-piotr.kubaj@intel.com>
Hi Piotr,
On Thu, 13 Aug 2026, Piotr Kubaj wrote:
> pmc_core: add test for pkgc_blocker_residency_show
> +static void setup(void)
> +{
> + if (access(DEBUGFS, F_OK))
> + tst_brk(TCONF | TERRNO, "debugfs not mounted at " DEBUGFS);
> +
> + if (access(PATH, R_OK))
> + tst_brk(TCONF | TERRNO, "%s not available", PATH);
> +}
Could the test mount debugfs when it is not already mounted, and unmount only
a test-created mount in cleanup?
On a supported Nova Lake system with debugfs unmounted,
/sys/kernel/debug still exists as the mount-point directory. The first
check therefore succeeds, and the missing counter path makes the test report
TCONF without testing the supported interface.
Verdict - Needs revision
---
Note:
The agent can sometimes produce false positives although often its
findings are genuine. If you find issues with the review, please
comment this email or ignore the suggestions.
Regards,
LTP AI Reviewer
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-08-13 10:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 9:45 [LTP] [PATCH v2] pmc_core: add test for pkgc_blocker_residency_show Piotr Kubaj
2026-08-13 9:48 ` Andrea Cervesato via ltp
2026-08-13 10:46 ` Kubaj, Piotr
2026-08-13 10:11 ` linuxtestproject.agent [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-11 16:28 [LTP] [PATCH] " Piotr Kubaj
2026-08-11 17:10 ` [LTP] " linuxtestproject.agent
2026-08-13 7:05 ` 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=20260813101140.9156-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=ltp@lists.linux.it \
--cc=piotr.kubaj@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.