Skip to contentSkip to conversation

"BindMounts" test failure

LTP Mitani 2 participants 2 messages Dec 17, 2009 – Dec 22, 2009

lore
Share & tools
lore

Mitani

author
#0 lore raw

Hi,

I ran "runltp" with "ltp-2009-12-16" cvs.
And I found the following failure in "BindMounts" testcase:

------------
sh: /opt/ltp/testscripts/test_fs_bind.sh: Permission denied
------------

When I added execution permission and tested this testcase, the following errors occurred.

------------
ls: /opt/ltp/testcases/kernel/fs/fs_bind/move/test*: No such file or directory
ls: /opt/ltp/testcases/kernel/fs/fs_bind/bind/test*: No such file or directory
ls: /opt/ltp/testcases/kernel/fs/fs_bind/rbind/test*: No such file or directory
ls: /opt/ltp/testcases/kernel/fs/fs_bind/regression/test*: No such file or directory
------------

This error is caused by following:
(1) Execution files haven't permissions.
(2) "${LTPROOT}" directory isn't the current directory in which "make install" executed.
By default, "${LTPROOT}" directory is "/opt/ltp".
(3) ".../ltp-2009-12-16/testcases/kernel/fs/fs_bind/" directory does exist, but "/opt/ltp/testcases/kernel/fs/fs_bind/" directory doesn't exist. (I want to suggest using "/opt/ltp/testcases/bin/fs_bind/" instead of "/opt/ltp/testcases/kernel/fs/fs_bind/".)

Then, I think that it requires following three modifications to run "BindMounts" test exactly:

(1) Add the execution permissions to "${LTPROOT}/testscripts" directory when installation.
(2) Deploy following four directories under the "${LTPROOT}/testcases/bin"

     directory when installation.
     "./fs_bind/move/"
     "./fs_bind/bind/"
     "./fs_bind/rbind/"
     "./fs_bind/regression/"

(3) Apply the following patch:
============

test_fs_bind.sh.new renamed from test_fs_bind.sh +1 -1
@@ -60,7 +60,7 @@
 		LTPROOT="${PWD}"
 	fi
 	
-	FS_BIND_ROOT="${LTPROOT}/testcases/kernel/fs/fs_bind"
+	FS_BIND_ROOT="${LTPROOT}/testcases/bin/fs_bind"
 
 	total=0 # total number of tests
 	for dir in "${test_dirs[@]}" ; do

============

Regards--

-Tomonori Mitani

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

#1 lore raw
Quoted 52 lines · Mitani

Hi,

I ran "runltp" with "ltp-2009-12-16" cvs.
And I found the following failure in "BindMounts" testcase:

------------
sh: /opt/ltp/testscripts/test_fs_bind.sh: Permission denied
------------

When I added execution permission and tested this testcase, the following errors occurred.

------------
ls: /opt/ltp/testcases/kernel/fs/fs_bind/move/test*: No such file or directory
ls: /opt/ltp/testcases/kernel/fs/fs_bind/bind/test*: No such file or directory
ls: /opt/ltp/testcases/kernel/fs/fs_bind/rbind/test*: No such file or directory
ls: /opt/ltp/testcases/kernel/fs/fs_bind/regression/test*: No such file or directory
------------

This error is caused by following:
 (1) Execution files haven't permissions.
 (2) "${LTPROOT}" directory isn't the current directory in which "make install" executed.
    By default, "${LTPROOT}" directory is "/opt/ltp".
 (3) ".../ltp-2009-12-16/testcases/kernel/fs/fs_bind/" directory does exist, but "/opt/ltp/testcases/kernel/fs/fs_bind/" directory doesn't exist. (I want to suggest using "/opt/ltp/testcases/bin/fs_bind/" instead of "/opt/ltp/testcases/kernel/fs/fs_bind/".)

Then, I think that it requires following three modifications to run "BindMounts" test exactly:

 (1) Add the execution permissions to "${LTPROOT}/testscripts" directory when installation.
 (2) Deploy following four directories under the "${LTPROOT}/testcases/bin" directory when installation.
    "./fs_bind/move/"
    "./fs_bind/bind/"
    "./fs_bind/rbind/"
    "./fs_bind/regression/"
 (3) Apply the following patch:
============

test_fs_bind.sh.new 2009-12-17 11:32:27.000000000 +0900 renamed from test_fs_bind.sh     2008-06-29 04:30:19.000000000 +0900 +0 -0
@@ -60,7 +60,7 @@

               LTPROOT="${PWD}"
       fi

Quoted 5 lines

-       FS_BIND_ROOT="${LTPROOT}/testcases/kernel/fs/fs_bind"
+       FS_BIND_ROOT="${LTPROOT}/testcases/bin/fs_bind"

       total=0 # total number of tests
       for dir in "${test_dirs[@]}" ; do

The install issues should be fixed now, but there may be some
issues with mountpoints, et all so please holler if you run into any functional issues with the test.
Thanks,
-Garrett

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list