From: Bian Naimeng <biannm@cn.fujitsu.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: [LTP] [POSIX][PATCH]Fix bug of script implemented tests
Date: Wed, 23 Feb 2011 15:02:56 +0800 [thread overview]
Message-ID: <4D64B120.5010004@cn.fujitsu.com> (raw)
Tests implemented by script will fail, because they try to invoke a inexistent binary file.
[root@Linux sigaddset]# ./1-1.sh
./1-1.sh: line 20: conformance/interfaces/sigaddset/1-core-buildonly.test: No such file or directory
It's a widespread problem on the latest LTP.
Signed-off-by: Bian Naimeng <biannm@cn.fujitsu.com>
---
.../conformance/interfaces/sigaddset/1-1.sh | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/testcases/open_posix_testsuite/conformance/interfaces/sigaddset/1-1.sh b/testcases/open_posix_testsuite/conformance/interfaces/sigaddset/1-1.sh
index e12c69e..e77ed54 100755
--- a/testcases/open_posix_testsuite/conformance/interfaces/sigaddset/1-1.sh
+++ b/testcases/open_posix_testsuite/conformance/interfaces/sigaddset/1-1.sh
@@ -17,4 +17,4 @@
# Calling 1-core-buildonly.test with a 0 parameter initializes to an
# empty set.
-conformance/interfaces/sigaddset/1-core-buildonly.test 0
+./1-core 0
--
1.7.0.4
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT data
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2011-02-23 7:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 7:02 Bian Naimeng [this message]
2011-02-23 7:48 ` [LTP] [POSIX][PATCH]Fix bug of script implemented tests Garrett Cooper
2011-02-24 1:14 ` Peng Haitao
2011-02-24 5:27 ` Garrett Cooper
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=4D64B120.5010004@cn.fujitsu.com \
--to=biannm@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=yanegomi@gmail.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 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.