From: Zhang, Yixin <yixin.zhang@intel.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH ltp] runtest/{ltplite, stress.part1}: update commands for gf01-30/rwtest01-05
Date: Wed, 15 Aug 2018 14:54:58 +0800 [thread overview]
Message-ID: <20180815065458.GA19549@yixin-desktop> (raw)
In-Reply-To: <20180726130439.GA12339@dell5510>
Hi Petr,
Sorry for late response. I've merge fs_inod01/iogen01 into the v2 of this patch
as you suggested.
The initial reason I created these patches is that I saw there are duplicated
test cases name in same or different runtest files, some of them even with
same name but different commands! To me this bring some difficulty when I try
to manager all test results in a database (same test name but different cmd).
Example in runtest/stress.part1:
nfs01 export VERSION=2 SOCKET_TYPE=udp; nfs01
nfs01 export VERSION=2 SOCKET_TYPE=tcp; nfs01
nfs01 export VERSION=3 SOCKET_TYPE=udp; nfs01
nfs01 export VERSION=3 SOCKET_TYPE=tcp; nfs01
nfs02 export VERSION=2 SOCKET_TYPE=udp; nfs02
nfs02 export VERSION=2 SOCKET_TYPE=tcp; nfs02
nfs02 export VERSION=3 SOCKET_TYPE=udp; nfs02
nfs02 export VERSION=3 SOCKET_TYPE=tcp; nfs02
So I'm trying to clean all these, starting from fs part. I think that will help
if you decide to remove runtest/stress.part[1-3] and runtest/ltplite. If you
like I can alos provide a full list of such kind of tests.
Yixin
On 2018-07-26 at 15:04:39 +0200, Petr Vorel wrote:
> Hi Yixin,
>
> > gf01-30/rwtest01-05 are orignal defined in runtest file 'fs', and they
> > are updated multiple times in file 'fs' but missed in 'ltplite'/'stress.part1'.
> > So this patch copy all updates to the tests in 'ltplite'/'stress.part1'.
>
> > Ref:
> > c9dd96e6b2f811dbad119c3558d90cb7dfc3919b
> > 95e8b61433efcefb83699aaf859e92ad2b576373
> > 606e544932248858f65c7ab3061f77c542c07cfe
>
> > Signed-off-by: Yixin Zhang <yixin.zhang@intel.com>
>
> I wonder if we want to keep these runtest/stress.part[1-3] and runtest/ltplite
> files. ATM we don't have feature to include runtest files (among other problems
> with test runner), but keeping this duplicity doesn't look to me.
>
>
> Kind regards,
> Petr
prev parent reply other threads:[~2018-08-15 6:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 8:49 [LTP] [PATCH ltp] runtest/{ltplite, stress.part1}: update commands for gf01-30/rwtest01-05 Yixin Zhang
2018-07-26 13:04 ` Petr Vorel
2018-07-30 13:08 ` Jan Stancek
2018-08-15 6:54 ` Zhang, Yixin [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=20180815065458.GA19549@yixin-desktop \
--to=yixin.zhang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox