From: linuxtestproject.agent@gmail.com
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] metadata: add tests grouping support
Date: Mon, 22 Jun 2026 09:57:53 +0000 [thread overview]
Message-ID: <20260622095753.3979-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260622-metadata_groups-v3-1-45651d685c3c@suse.com>
Hi Andrea,
On Mon, 22 Jun 2026, Andrea Cervesato wrote:
> metadata: add tests grouping support
--- [PATCH 1/2] ---
> +static int parse_groups(struct data_node *groups, char *line)
> +{
> + s += sizeof(GROUPS_TAG) - 1;
> + if (*s && *s != ' ' && *s != '\t') {
> + WARN("Empty @group");
> + return 1;
> + }
Two things here:
The warning says "@group" (singular) but the tag is "@groups". More
importantly, this condition fires when "@groups" is immediately followed
by a non-whitespace character (e.g. "@groupsfoo"), which is not an
empty tag but a word that happens to share a prefix with the tag. The
message should probably say something like "invalid @groups suffix".
Separately, a truly empty "@groups" line (tag followed by nothing or
only whitespace) falls through to strtok which produces zero tokens and
returns 1 silently. Should that also warn?
> + /* inside the testcases/ folder we will always have at least one group */
> + data_node_hash_add(res, "groups", groups);
The comment is not accurate. A file like testcases/kernel/foo.c with
no @groups tags produces zero groups since "kernel" is the only parent
directory and is explicitly skipped.
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-06-22 9:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 8:53 [LTP] [PATCH v3 0/2] Support metadata groups Andrea Cervesato
2026-06-22 8:53 ` [LTP] [PATCH v3 1/2] metadata: add tests grouping support Andrea Cervesato
2026-06-22 9:57 ` linuxtestproject.agent [this message]
2026-06-22 9:59 ` Cyril Hrubis
2026-06-22 10:48 ` Andrea Cervesato via ltp
2026-06-22 11:15 ` Cyril Hrubis
2026-06-22 11:59 ` Andrea Cervesato via ltp
2026-06-22 12:08 ` Cyril Hrubis
2026-06-22 8:53 ` [LTP] [PATCH v3 2/2] doc: conf.py: Show groups in test catalog Andrea Cervesato
-- strict thread matches above, loose matches on Subject: below --
2026-06-18 14:10 [LTP] [PATCH v2 1/2] metadata: add tests grouping support Andrea Cervesato
2026-06-18 16:40 ` [LTP] " linuxtestproject.agent
2026-06-12 13:54 [LTP] [PATCH 1/2] " Andrea Cervesato
2026-06-12 19:10 ` [LTP] " linuxtestproject.agent
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=20260622095753.3979-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=andrea.cervesato@suse.de \
--cc=ltp@lists.linux.it \
/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.