From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [RFC PATCH 1/2] Add support for mixing C and shell code
Date: Thu, 18 Jul 2024 15:15:36 +0200 [thread overview]
Message-ID: <20240718131536.GB739726@pevik> (raw)
In-Reply-To: <ZpkTmcvKtJeTsU_N@yuki>
> Hi!
> > > This is a proof of a concept of a seamless C and shell integration. The
> > > idea is that with this you can mix shell and C code as much as as you
> > > wish to get the best of the two worlds.
> > > Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
> > > ---
> > > include/tst_test.h | 38 +++++++++++++
> > > lib/tst_test.c | 51 +++++++++++++++++
> > > testcases/lib/.gitignore | 1 +
> > > testcases/lib/Makefile | 4 +-
> > > testcases/lib/run_tests.sh | 10 ++++
> > > testcases/lib/tests/.gitignore | 6 ++
> > > testcases/lib/tests/Makefile | 11 ++++
> > > testcases/lib/tests/shell_loader.sh | 5 ++
> > > testcases/lib/tests/shell_test01.c | 17 ++++++
> > > testcases/lib/tests/shell_test02.c | 18 ++++++
> > > testcases/lib/tests/shell_test03.c | 25 +++++++++
> > > testcases/lib/tests/shell_test04.c | 18 ++++++
> > > testcases/lib/tests/shell_test05.c | 27 +++++++++
> > > testcases/lib/tests/shell_test06.c | 16 ++++++
> > FYI we have shell tests for new library in lib/newlib_tests (C tests) and
> > lib/newlib_tests/shell/ (shell tests), is it necessary to add new location? Or,
> > if you prefer this, we should move existing tests from lib/newlib_tests/shell/
> > to this new location.
> For a historical reasons the lib for shell is in testcases/lib/ and the
> tests use paths to binaries and scripts in there so I added the code
> there. We may as well move it to the top level lib/shell, or create top
> level slib (as for shell lib) or anywhere else as long as we agree on a
> better place to put the code.
Yeah, we could move everything to lib/shell. I'm also OK with different location
with the tests, i.e. we can keep things where they are.
My main concern is to run the tests in CI and in 'make test' target (also
specify new subtest e.g. test-c-shell: or add them to test-c).
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-07-18 13:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 15:36 [LTP] [RFC PATCH 0/2] Shell test library v3 Cyril Hrubis
2024-07-16 15:36 ` [LTP] [RFC PATCH 1/2] Add support for mixing C and shell code Cyril Hrubis
2024-07-17 8:33 ` Li Wang
2024-07-17 8:41 ` Cyril Hrubis
2024-07-17 10:07 ` Li Wang
2024-07-17 8:52 ` Cyril Hrubis
2024-07-17 10:21 ` Li Wang
2024-07-17 17:51 ` Petr Vorel
2024-07-17 17:55 ` Petr Vorel
2024-07-17 18:13 ` Cyril Hrubis
2024-07-18 12:43 ` Petr Vorel
2024-07-18 13:03 ` Cyril Hrubis
2024-07-18 12:57 ` Petr Vorel
2024-07-18 13:07 ` Cyril Hrubis
2024-07-18 13:15 ` Petr Vorel [this message]
2024-07-24 9:37 ` Martin Doucha
2024-07-24 9:47 ` Cyril Hrubis
2024-07-24 9:53 ` Martin Doucha
2024-07-24 10:05 ` Cyril Hrubis
2024-07-30 9:49 ` Cyril Hrubis
2024-07-16 15:36 ` [LTP] [RFC PATCH 2/2] testcaes/lib: Add shell loader Cyril Hrubis
2024-07-24 12:54 ` Martin Doucha
2024-07-25 11:02 ` Petr Vorel
2024-07-25 16:01 ` Martin Doucha
2024-07-25 21:44 ` Petr Vorel
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=20240718131536.GB739726@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox