From: Sachin Sant <sachinp@in.ibm.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] LTP Containers netns test failure.
Date: Fri, 12 Mar 2010 10:39:36 +0530 [thread overview]
Message-ID: <4B99CC90.90204@in.ibm.com> (raw)
In-Reply-To: <364299f41003102015j42667189x9adbc23f48121e87@mail.gmail.com>
Garrett Cooper wrote:
> On Wed, Mar 10, 2010 at 6:20 AM, Sachin Sant <sachinp@in.ibm.com> wrote:
>
>> NETNS tests from containers fails to execute with following
>> message
>>
>> Running netns tests.
>> --: childns.sh '/opt/ltp': No such file or directory
>>
>> Looking at the code the problem could be with create_net_namespace()
>> within netns/common.c
>>
>> If i make the following changes the first subtest works fine but then
>> i ran into other failures related to other sub tests.
>>
>> @@ -92,7 +92,7 @@ int create_net_namespace(char *p1, char
>> }
>>
>> /* We need to pass the child pid to the parentns.sh script */
>> - sprintf(par, "parentns.sh '%s' %s %" PRId32 , ltproot, p1, pid);
>> + sprintf(par, "%s/testcases/bin/parentns.sh %s %" PRId32 , ltproot,
>> p1, pid);
>>
>> ret = system(par);
>> status = WEXITSTATUS(ret);
>> @@ -141,7 +141,7 @@ int child_fn(void *c1)
>> exit(1);
>> }
>>
>> - sprintf(child, "childns.sh '%s'", ltproot);
>> + sprintf(child, "%s/testcases/bin/childns.sh", ltproot);
>>
>> As i don't know the code too much .. i am not sure how to fix it.
>>
>
> export PATH=$PATH:$LTPROOT/testcases/bin ; parentns.sh ?
>
> Why are you overcomplicating things by hardcoding the path again?
> That's the exact reason why it was removed in the first place...
>
Hmm .. i am still not able to execute the test even after exporting the
PATH.
lp5:/opt/ltp # export LTPROOT=/opt/ltp
lp5:/opt/ltp # export PATH=$PATH:$LTPROOT/testcases/bin
lp5:/opt/ltp # ./runltp -f containers
........<SNIP>..........
<<<test_start>>>
tag=Containers stime=1268369850
cmdline="container_test.sh"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
Running netns tests.
--: childns.sh '/opt/ltp': No such file or directory
I feel the problem is: the code is searching childns.sh in LTPROOT
directory instead of LTPROOT/testcases/bin
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2010-03-12 5:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 14:20 [LTP] LTP Containers netns test failure Sachin Sant
2010-03-11 4:15 ` Garrett Cooper
2010-03-12 5:09 ` Sachin Sant [this message]
2010-03-12 7:33 ` Garrett Cooper
2010-03-12 8:56 ` Sachin Sant
2010-03-12 16:32 ` Garrett Cooper
2010-03-15 7:03 ` Sachin Sant
2010-03-31 8:12 ` Rishikesh K Rajak
2010-03-31 8:15 ` 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=4B99CC90.90204@in.ibm.com \
--to=sachinp@in.ibm.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.