From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] commands: fix unmatched installation path of datafiles
Date: Mon, 3 Jul 2017 10:14:31 +0800 [thread overview]
Message-ID: <5959A887.5060405@cn.fujitsu.com> (raw)
In-Reply-To: <20170630114037.GB18305@rei.lan>
On 2017/06/30 19:40, Cyril Hrubis wrote:
> Hi!
>> Both file01 and unzip01 fail due to unmatched installation
>> path of datafiles. It has been broken by:
>>
>> commit f9a91c164ac52a4c91ff6aa9c156f110d04158d6
>> Author: Li Wang<liwang@redhat.com>
>> Date: Wed May 24 15:18:31 2017 +0800
>>
>> tst_tests.sh: set the shell TST_ID automatically
>>
>> We need to change installation path of datafiles to fix it.
> Good catch, but I would be happier if we simply renamed the testcases to
> keep the test filenames constistent. Can you please post that patch
> instead?
Hi Cyril
Thanks for your comment. I will send v2 patch as you suggested.
Thanks,
Xiao Yang
next prev parent reply other threads:[~2017-07-03 2:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 3:40 [LTP] [PATCH] commands: fix unmatched installation path of datafiles Xiao Yang
2017-06-30 11:40 ` Cyril Hrubis
2017-07-03 2:14 ` Xiao Yang [this message]
2017-07-03 2:36 ` [LTP] [PATCH v2] " Xiao Yang
2017-07-04 11:36 ` Cyril Hrubis
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=5959A887.5060405@cn.fujitsu.com \
--to=yangx.jy@cn.fujitsu.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