From: Rishikesh K Rajak <risrajak@linux.vnet.ibm.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [BUG?] container_test.sh: should to delete check_for_unshare's source in cvs/git ?
Date: Mon, 8 Mar 2010 22:47:07 +0530 [thread overview]
Message-ID: <20100308171707.GA4999@linux.vnet.ibm.com> (raw)
In-Reply-To: <364299f41003080753h78ddb8c0uc20027ccf2e3c990@mail.gmail.com>
On Mon, Mar 08, 2010 at 07:53:08AM -0800, Garrett Cooper wrote:
> On Sun, Mar 7, 2010 at 6:56 PM, Shi Weihua <shiwh@cn.fujitsu.com> wrote:
> > Tested the latest cvs version (about Mar 1) on my x86_64 (2.6.33).
> > The following message occured:
> > --------------------------------
> > <<<test_start>>>
> > tag=Containers stime=1267527554
> > cmdline="container_test.sh"
> > contacts=""
> > analysis=exit
> > <<<test_output>>>
> > /opt/ltp/testcases/bin/container_test.sh: line 13: check_for_unshare: command not found
> > Running utsns tests.
> > unshare tests
> > test 1 (unshare)
> > test 2 (unshare)
> > ......
> > --------------------------------
> >
> > I noticed that check_for_unshare had been deleted in LTP-20091031.
> > In ./ChangeLog (from latest cvs version)
> > ...
> > 2905 LTP-20091031
> > ...
> > 3141 Removed Files:
> > 3142 ltp/README.ltp-devel
> > 3143 ltp/config.mk.in
> > 3144 ltp/ltp-devel.spec
> > 3145 ltp/testcases/kernel/containers/check_for_unshare.c
> > ...
> > 3997 LTP-20090930
> >
> > Also, i noticed check_for_unshare commentted in container_test.sh in
> > release version of FEBRUARY 2010. pls check the diff between cvs version
> > and release version of Feb in attached file.
> >
> > Now, my question: should to delete check_for_unshare's source in cvs/git ?
>
> There was some discussion and the check was reenabled post the February release.
I looked at a glance in sleep mode and found there is something need to
be fixed here as i am still not able to find check_for_unshare.c . Well
i will look and fix tomorrow.
Thanks
Rishi
> Thanks,
> -Garrett
--
Thanks & Regards
Rishi
LTP Maintainer
IBM, LTC, Bangalore
Please join IRC #ltp @ irc.freenode.net
------------------------------------------------------------------------------
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-08 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 2:56 [LTP] [BUG?] container_test.sh: should to delete check_for_unshare's source in cvs/git ? Shi Weihua
2010-03-08 15:53 ` Garrett Cooper
2010-03-08 17:17 ` Rishikesh K Rajak [this message]
2010-03-09 8:39 ` Rishikesh K Rajak
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=20100308171707.GA4999@linux.vnet.ibm.com \
--to=risrajak@linux.vnet.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.