From: "Mitani" <mitani@ryobi.co.jp>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] move_pages test failed in ltp-2009-11-19.tar.gz
Date: Fri, 20 Nov 2009 15:00:58 +0900 [thread overview]
Message-ID: <000001ca69a6$d6ad7520$84085f60$@co.jp> (raw)
Hi,
When I ran LTP in RHEL5.4 using ltp-2009-11-19.tar.gz,
"move_pages03" and "move_pages11" were failed in each of "syscalls" and
"numa" tests like that:
------------
move_pages01 1 TCONF : NUMA support not provided
move_pages02 1 TCONF : NUMA support not provided
chown: cannot access `move_pages03': No such file or directory
move_pages04 1 TCONF : NUMA support not provided
move_pages05 1 TCONF : NUMA support not provided
move_pages06 1 TCONF : NUMA support not provided
move_pages07 1 TCONF : NUMA support not provided
move_pages08 1 TCONF : NUMA support not provided
move_pages09 1 TCONF : NUMA support not provided
move_pages10 1 TCONF : NUMA support not provided
chown: cannot access `move_pages11': No such file or directory
------------
These fails didn't occured with ltp-full-20090930.tgz, but they occured
with ltp-full-20091031.tgz.
With ltp-full-20090930.tgz, all of move_pagesXX (XX:01-11) were passed
(NUMA support not provided) in my system.
I compared these version and found out following scenarios changed.
- ${LTPROOT}/runtest/numa
- ${LTPROOT}/runtest/syscalls
These scenarios are as follows, and "move_pages03" and "move_pages01"
are revised.
------------
# cat ./runtest/numa
Numa-testcases numa01.sh
move_pages01 move_pages.sh 01
move_pages02 move_pages.sh 02
move_pages03 cd $LTPROOT/bin && chown root move_pages03 && chmod 04755 &&
move_pages.sh 03
move_pages04 move_pages.sh 04
move_pages05 move_pages.sh 05
move_pages06 move_pages.sh 06
move_pages07 move_pages.sh 07
move_pages08 move_pages.sh 08
move_pages09 move_pages.sh 09
move_pages10 move_pages.sh 10
move_pages11 cd $LTPROOT/bin && chown root move_pages11 && chmod 04755 &&
move_pages.sh 11
# cat ./runtest/syscalls | grep move_page
move_pages01 move_pages.sh 01
move_pages02 move_pages.sh 02
move_pages03 cd $LTPROOT/bin && chown root move_pages03 && chmod 04755 &&
move_pages.sh 03
move_pages04 move_pages.sh 04
move_pages05 move_pages.sh 05
move_pages06 move_pages.sh 06
move_pages07 move_pages.sh 07
move_pages08 move_pages.sh 08
move_pages09 move_pages.sh 09
move_pages10 move_pages.sh 10
move_pages11 cd $LTPROOT/bin && chown root move_pages11 && chmod 04755 &&
move_pages.sh 11
#------------
I think there are two problems in each changes:
- "move_pagesXX" files are in "$LTPROOT/testcases/bin" direcotory,
not in "$LTPROOT/bin" directory.
- "chmod" commands don't have target file.
I don't know why these revisions are done. But if these revisions should
be validated, they will come to work in the change like following, I think.
I wish I can get opinion whether my revision is right or not.
============
--- syscalls 2009-11-18 13:24:34.000000000 +0900
+++ syscalls.new 2009-11-19 16:15:13.000000000 +0900
@@ -571,7 +571,7 @@
move_pages01 move_pages.sh 01
move_pages02 move_pages.sh 02
-move_pages03 cd $LTPROOT/bin && chown root move_pages03 && chmod 04755 &&
move_pages.sh 03
+move_pages03 cd $LTPROOT/testcases/bin && chown root move_pages03 && chmod
04755 move_pages.sh && move_pages.sh 03
move_pages04 move_pages.sh 04
move_pages05 move_pages.sh 05
move_pages06 move_pages.sh 06
@@ -579,7 +579,7 @@
move_pages08 move_pages.sh 08
move_pages09 move_pages.sh 09
move_pages10 move_pages.sh 10
-move_pages11 cd $LTPROOT/bin && chown root move_pages11 && chmod 04755 &&
move_pages.sh 11
+move_pages11 cd $LTPROOT/testcases/bin && chown root move_pages11 && chmod
04755 move_pages.sh && move_pages.sh 11
mprotect01 mprotect01
mprotect02 mprotect02
--- numa 2009-11-18 13:24:34.000000000 +0900
+++ numa.new 2009-11-19 16:15:33.000000000 +0900
@@ -1,7 +1,7 @@
Numa-testcases numa01.sh
move_pages01 move_pages.sh 01
move_pages02 move_pages.sh 02
-move_pages03 cd $LTPROOT/bin && chown root move_pages03 && chmod 04755 &&
move_pages.sh 03
+move_pages03 cd $LTPROOT/testcases/bin && chown root move_pages03 && chmod
04755 move_pages.sh && move_pages.sh 03
move_pages04 move_pages.sh 04
move_pages05 move_pages.sh 05
move_pages06 move_pages.sh 06
@@ -9,4 +9,4 @@
move_pages08 move_pages.sh 08
move_pages09 move_pages.sh 09
move_pages10 move_pages.sh 10
-move_pages11 cd $LTPROOT/bin && chown root move_pages11 && chmod 04755 &&
move_pages.sh 11
+move_pages11 cd $LTPROOT/testcases/bin && chown root move_pages11 && chmod
04755 move_pages.sh && move_pages.sh 11
============
In addition, please teach why this revision was performed, if all right.
- Why do only "move_pages03" and "move_pages11" appoint another directory
not a current directory?
- Why "chmod" is needed?
Thank you--
-Tomonori Mitani
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2009-11-20 6:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 6:00 Mitani [this message]
2009-11-20 6:24 ` [LTP] move_pages test failed in ltp-2009-11-19.tar.gz Garrett Cooper
2009-12-04 18:00 ` Jiri Palecek
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='000001ca69a6$d6ad7520$84085f60$@co.jp' \
--to=mitani@ryobi.co.jp \
--cc=ltp-list@lists.sourceforge.net \
/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