From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3 4/4] testcaes/lib: Add shell loader
Date: Mon, 16 Sep 2024 12:04:47 +0200 [thread overview]
Message-ID: <ZugCv08Io4PGpnue@yuki.lan> (raw)
In-Reply-To: <90cf8a7d-7c93-470d-a33d-816b513730cd@suse.com>
Hi!
> > +static void extract_metadata(void)
> > +{
> > + FILE *f;
> > + char line[4096];
> > + char path[4096];
> > + enum parser_state state = PAR_NONE;
> > +
> > + if (tst_get_path(shell_filename, path, sizeof(path)) == -1)
> > + tst_brk(TBROK, "Failed to find %s in $PATH", shell_filename);
> > +
> > + f = SAFE_FOPEN(path, "r");
> > +
> > + while (fgets(line, sizeof(line), f)) {
> > + switch (state) {
> > + case PAR_NONE:
> > + if (!strcmp(line, "# ---\n"))
> What if user defines "#---" or "# ---" ? IMHO it would be better to
> parse it following shell comments standards. In particular, "^#\s+---"
> using a *scan function.
If user sets the line any differently the test will end up with pretty
clear error message that metadata are missing, so I do not see this as
an issue.
> > + state = PAR_ESC;
> > + break;
> > + case PAR_ESC:
> > + if (!strcmp(line, "# env\n"))
> Same apply here and to the others.
Same here as well.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-09-16 10:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 12:02 [LTP] [PATCH v3 0/4] Shell test library v3 Cyril Hrubis
2024-08-27 12:02 ` [LTP] [PATCH v3 1/4] include: tst_clone.h: Fix possible MUSL build failures Cyril Hrubis
2024-09-03 7:46 ` Petr Vorel
2024-09-03 8:02 ` Cyril Hrubis
2024-08-27 12:02 ` [LTP] [PATCH v3 2/4] Add support for mixing C and shell code Cyril Hrubis
2024-08-30 12:40 ` Andrea Cervesato via ltp
2024-09-03 7:29 ` Li Wang
2024-09-03 8:24 ` Petr Vorel
2024-09-16 9:52 ` Cyril Hrubis
2024-09-06 7:34 ` Li Wang
2024-09-06 9:53 ` Cyril Hrubis
2024-09-06 10:03 ` Cyril Hrubis
2024-09-06 10:09 ` Li Wang
2024-09-06 11:22 ` Cyril Hrubis
2024-09-06 13:28 ` Cyril Hrubis
2024-09-07 1:29 ` Li Wang
2024-09-06 10:19 ` Li Wang
2024-09-06 11:06 ` Li Wang
2024-08-27 12:02 ` [LTP] [PATCH v3 3/4] libs: Vendor ujson library Cyril Hrubis
2024-08-30 12:41 ` Andrea Cervesato via ltp
2024-09-16 9:58 ` Cyril Hrubis
2024-08-27 12:02 ` [LTP] [PATCH v3 4/4] testcaes/lib: Add shell loader Cyril Hrubis
2024-08-30 12:47 ` Andrea Cervesato via ltp
2024-09-16 10:04 ` Cyril Hrubis [this message]
2024-08-30 12:50 ` Andrea Cervesato via ltp
2024-09-16 10:02 ` Cyril Hrubis
2024-09-09 9:03 ` Li Wang
2024-09-16 10:08 ` [LTP] [PATCH v3 0/4] Shell test library v3 Cyril Hrubis
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=ZugCv08Io4PGpnue@yuki.lan \
--to=chrubis@suse.cz \
--cc=andrea.cervesato@suse.com \
--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.