From: linuxtestproject.agent@gmail.com
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] Makefile: Skip test-metadata on cross compile
Date: Fri, 10 Jul 2026 08:30:37 +0000 [thread overview]
Message-ID: <20260710083037.4145-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260710055556.1109220-2-pvorel@suse.cz>
Hi Petr,
On Fri, 10 Jul 2026 07:55:49 +0200, Petr Vorel wrote:
> Makefile: Skip test-metadata on cross compile
--- [PATCH 2/8] ---
> + printf "* $i "
$i is used directly as part of the printf format string rather than
passed as a separate argument. A filename containing a '%' character
would be interpreted as a format specifier.
The portable form is:
printf "* %s " "$i"
--- [PATCH 4/8] ---
> + $METAPARSE $i > tmp.json
Both $METAPARSE and $i are unquoted. If METAPARSEDIR (and therefore
METAPARSE) contains spaces, the shell will perform word-splitting on
the variable before exec, breaking the invocation.
The quoted form:
"$METAPARSE" "$i" > tmp.json
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-07-10 8:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 5:55 [LTP] [PATCH v2 0/7] CI: Run metadata tests Petr Vorel
2026-07-10 5:55 ` [LTP] [PATCH v2 1/8] Makefile: Skip test-metadata on cross compile Petr Vorel
2026-07-10 8:29 ` [LTP] " linuxtestproject.agent
2026-07-10 8:30 ` linuxtestproject.agent [this message]
2026-07-10 5:55 ` [LTP] [PATCH v2 2/8] metadata: test.sh: Print the test name and result Petr Vorel
2026-07-10 6:06 ` Petr Vorel
2026-07-13 11:01 ` Andrea Cervesato via ltp
2026-07-10 5:55 ` [LTP] [PATCH v2 3/8] metadata: Fix dependency for tests Petr Vorel
2026-07-13 11:01 ` Andrea Cervesato via ltp
2026-07-10 5:55 ` [LTP] [PATCH v2 4/8] metadata: test.sh: Add support for building out-of-tree Petr Vorel
2026-07-10 9:01 ` Cyril Hrubis
2026-07-10 11:39 ` Petr Vorel
2026-07-10 11:47 ` Cyril Hrubis
2026-07-13 9:19 ` Andrea Cervesato via ltp
2026-07-13 9:46 ` Cyril Hrubis
2026-07-13 10:53 ` Andrea Cervesato via ltp
2026-07-13 15:26 ` Cyril Hrubis
2026-07-13 11:05 ` Andrea Cervesato via ltp
2026-07-10 5:55 ` [LTP] [PATCH v2 5/8] metadata: Add missing licenses, copyright Petr Vorel
2026-07-13 11:05 ` Andrea Cervesato via ltp
2026-07-10 5:55 ` [LTP] [PATCH v2 6/8] build.sh: Add support for test-metadata Petr Vorel
2026-07-13 11:11 ` Andrea Cervesato via ltp
2026-07-10 5:55 ` [LTP] [PATCH v2 7/8] ci/tumbleweed: Install diffutils Petr Vorel
2026-07-13 11:11 ` Andrea Cervesato via ltp
2026-07-10 5:55 ` [LTP] [PATCH v2 8/8] ci: Test metadata in docker build testing Petr Vorel
2026-07-13 11:12 ` 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=20260710083037.4145-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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.