From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] file01.sh: Fix in was not recognized
Date: Mon, 22 Apr 2019 10:55:16 +0800 [thread overview]
Message-ID: <5CBD2D14.9060905@cn.fujitsu.com> (raw)
In-Reply-To: <1555896566-317528-1-git-send-email-zhe.he@windriver.com>
On 2019/04/22 9:29, zhe.he@windriver.com wrote:
> From: He Zhe<zhe.he@windriver.com>
>
> Some file may have "pie" and possible other things appending after LSB or MSB,
> which causes mismatch and the following error.
>
> "file01 10 TFAIL: in: was not recognized"
> ..."ELF 64-bit LSB pie executable"...
>
> This patches tunes the regulation expression to match those cases.
Hi He,
Your patch doesn't match original output(e.g. "...ELF 64-bit LSB
executable...").
Besides, could you tell me what kind of environment or operation can
reproduce
above unrecognized output?
Best Regards,
Xiao Yang
> Signed-off-by: He Zhe<zhe.he@windriver.com>
> ---
> testcases/commands/file/file01.sh | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/testcases/commands/file/file01.sh b/testcases/commands/file/file01.sh
> index 0a8119e..34274c3 100755
> --- a/testcases/commands/file/file01.sh
> +++ b/testcases/commands/file/file01.sh
> @@ -90,8 +90,8 @@ do_test()
> "[pP]ython3\{0,1\} script text executable";;
> 9) file_test in.m4 "M4 macro processor script, ASCII text" \
> "ASCII M4 macro language pre-processor text";;
> - 10) file_test in "ELF .*-bit $TEST_ARCH executable, .*" \
> - "ELF .*-bit $TEST_ARCH shared object, .*";;
> + 10) file_test in "ELF .*-bit $TEST_ARCH .* executable, .*" \
> + "ELF .*-bit $TEST_ARCH .* shared object, .*";;
> 11) file_test in.ar "current ar archive";;
> 12) file_test in.tar "tar archive";;
> 13) file_test in.tar.gz "gzip compressed data, .*";;
next prev parent reply other threads:[~2019-04-22 2:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 1:29 [LTP] [PATCH] file01.sh: Fix in was not recognized zhe.he
2019-04-22 2:55 ` Xiao Yang [this message]
2019-04-22 8:34 ` He Zhe
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=5CBD2D14.9060905@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 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.