On Tue, 2008-06-03 at 20:39 +0530, Subrata Modak wrote:
> ***********************
> Warning: Your file, fs_bind.tgz, contains more than 32 files after
> decompression and cannot be scanned.
> ***********************
>
>
> Rishi,
>
> I did not see these tests fail on:
>
> $ uname -a
> Linux <sniff> 2.6.18-53.1.13.el5 #1 SMP Mon Feb 11 13:27:52 EST 2008
> i686 i686 i386 GNU/Linux
>
> Please also see the attached results of fs_bind run.
>
> Regards--
> Subrata
>
>
> On Mon, 2008-06-02 at 22:08 +0530, Rishikesh K. Rajak wrote:
> > Hi All,
> >
> > I tried running fs_bind testcases running on my 64 bit system with
> > ltp-full-20080531 release, May be the way i am running be wrong. Can
> > anyone help me in that ?
> >
> > [EMAIL PROTECTED] move]# ./test01
> > test01 0 INFO : ***************TEST01***************
> > test01 0 INFO : move: shared child to shared parent.
> > test01 0 INFO : ************************************
> > ./test01: line 32: /bin/setup: No such file or directory
> > test01 0 WARN : Setup of move/test01 failed
> > ./test01: line 43: /bin/makedir: No such file or directory
> > test01 0 WARN : move/test01: caught error
> near: ./test01::63:
> > (returned 127)
> > test01 1 FAIL : move/test01: FAILED: move: shared child to
> > shared parent.
> >
> >
> > Additional Info:
> > Linux mx3250a 2.6.9-70.ELsmp #1 SMP Fri May 2 13:16:34 EDT 2008
> x86_64
> > x86_64 x86_64 GNU/Linux
> >
> > - All testcases of fs_bind are failing e.g: move, regression, bind
> > etc..
> >
> > Thanks
> > Rishi
Hi Rishi,
If you're just trying to run all of the testcases you can use
testscripts/test_fs_bind.sh
The README covers running the tests indvidually
(testcases/kernel/fs/fs_bind/README):
http://ltp.cvs.sourceforge.net/ltp/ltp/testcases/kernel/fs/fs_bind/README?view=markup
Specifically the section "Running individual Tests:". Though I think the
following is missing from this section of the README :(:
FS_BIND_ROOT="${LTPROOT}/testcases/kernel/fs/fs_bind"
export FS_BIND_ROOT
And I think you need to add these to your PATH:
LTPBIN="${LTPROOT}/testcases/bin"
PATH="${PATH}:/usr/sbin:${LTPBIN}:${FS_BIND_ROOT}/bin"
If you'd like to see an example of how to run the individual tests you
can also read testscripts/test_fs_bind.sh -- though it has lots of other
code to handle prereq testing, robust cleanup after each testcase, etc.
The tests are written this way so it's clear what the tests should be
testing for. Most of the setup, teardown, and unimportant intermediate
steps are factored out into functions in the setup script to avoid
distracting from the core of the test. "setup" and "makedir" are too
generic to place in the global testcases/bin directory -- hence the
scripts need "${FS_BIND_ROOT}/bin" in your PATH.
Keep in mind that depending on the test results the scripts may leave
mounts behind (though I tried to prevent this as best I could). That's
another reason they are wrapped in test_fs_bind.sh. You may find that
script helpful in learning to robustly clean up as well.
Cheers,
-Matt Helsley
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list
