From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Sachin Sant" <sachinp@linux.ibm.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v6 1/2] io_uring: Add test for READV and WRITEV operations
Date: Wed, 06 May 2026 11:45:20 +0000 [thread overview]
Message-ID: <69fb29d1.050a0220.1a0ae1.230e@mx.google.com> (raw)
In-Reply-To: <20260416121638.11858-1-sachinp@linux.ibm.com>
Hi Sachin,
is it possible to separate the test into multiple ones?
Having multiple tests scenarios inside a single binary means
that (often) if one scenario fails, the others can't be tested.
In the kernel maintenance it's important to keep distinction
between tested features, so it's easier to debug a bug
in the system by cross-checking different scenarios.
We can have a helper header sharing the common operations and
to define multiple test files. It's a common pattern we use
in LTP.
Regards,
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-05-06 11:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 12:16 [LTP] [PATCH v6 1/2] io_uring: Add test for READV and WRITEV operations Sachin Sant
2026-04-16 12:16 ` [LTP] [PATCH 2/2] io_uring: remove unused io_uring_init_buffer_pattern() Sachin Sant
2026-04-16 13:47 ` [LTP] io_uring: Add test for READV and WRITEV operations linuxtestproject.agent
2026-05-06 11:45 ` Andrea Cervesato via ltp [this message]
2026-05-06 12:11 ` [LTP] [PATCH v6 1/2] " Sachin Sant
2026-05-06 12:27 ` 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=69fb29d1.050a0220.1a0ae1.230e@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=sachinp@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox