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 12:27:12 +0000 [thread overview]
Message-ID: <69fb33a1.5d0a0220.337e29.6038@mx.google.com> (raw)
In-Reply-To: <27137773-c7b1-4e69-abda-7a5f422ca837@linux.ibm.com>
> On 06/05/26 5:15 pm, Andrea Cervesato wrote:
> > Hi Sachin,
> >
> > is it possible to separate the test into multiple ones?
> Sure, can be done. Do you have any specific inputs on how to
> split the test.
>
> Split it into three tests, one for each of the following:
>
> test_writev_readv();
> test_partial_vectors();
> test_varying_sizes();
>
They can be split yes.
>
> > Having multiple tests scenarios inside a single binary means
> > that (often) if one scenario fails, the others can't be tested.
> Got it. Just curious, did you run into any test failure.
No, mine was a general rule just in case we face it.
Regards,
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-05-06 12:27 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 ` [LTP] [PATCH v6 1/2] " Andrea Cervesato via ltp
2026-05-06 12:11 ` Sachin Sant
2026-05-06 12:27 ` Andrea Cervesato via ltp [this message]
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=69fb33a1.5d0a0220.337e29.6038@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