All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhang, Yixin <yixin.zhang@intel.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 ltp] runtest/{ltplite, stress.part1}: update commands for gf01-30/rwtest01-05/fs_inod01/iogen01
Date: Fri, 12 Oct 2018 10:39:56 +0800	[thread overview]
Message-ID: <20181012023956.GJ19438@yixin-dev> (raw)
In-Reply-To: <20181008132308.GA9870@dell5510>

Hi Petr,

I alos think we should remove the ltplite/stress.part* files. You will submit
a patch for that, right?

Yixin

On 2018-10-08 at 15:23:08 +0200, Petr Vorel wrote:
> Hi Yixin,
> 
> > gf01-30/rwtest01-05/fs_inod01/iogen01 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
> > b0458a3c838c86faf2d8855c097628c0c435532a
> 
> > Signed-off-by: Yixin Zhang <yixin.zhang@intel.com>
> > ---
> >  runtest/ltplite      | 71 +++++++++++++++++++++---------------------
> >  runtest/stress.part1 | 74 ++++++++++++++++++++++----------------------
> 
> while this change is correct, I'd prefer to delete these aggregated runtest files (ltplite,
> stress.part*) than keeping them in sync.
> 
> Another option is implement some import feature for ltp-pan. But I guess it's
> better to invest the effort into Cyril's new test runner [1].
> 
> Kind regards,
> Petr
> 
> [1] https://github.com/metan-ucw/ltp/commits/master

      reply	other threads:[~2018-10-12  2:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-15  6:44 [LTP] [PATCH v2 ltp] runtest/{ltplite, stress.part1}: update commands for gf01-30/rwtest01-05/fs_inod01/iogen01 Yixin Zhang
2018-10-08 13:23 ` Petr Vorel
2018-10-12  2:39   ` 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=20181012023956.GJ19438@yixin-dev \
    --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 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.