From: Shwetabh <shwetabh.goel@calsoftinc.com>
To: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Missing test tools in recent ltp builds
Date: Wed, 03 Mar 2010 18:32:43 +0530 [thread overview]
Message-ID: <4B8E5DF3.7090502@calsoftinc.com> (raw)
In-Reply-To: <20100303124352.GD23601@linux.vnet.ibm.com>
Hi Rishi,
Here is the information you needed:
- Installation Steps:
1. Downloaded LTP's Feb 2010 Stable build from ltp.sourceforge.net
2. Extracted/compiled using following commands:
tar -xzf ltp-full-20100228.tgz
cd ltp-full-20100228
./configure
make
make install
3. Went to /opt/ltp directory and tried to execute cpuhotplug test:
[root@localhost ~]# cd /opt/ltp/
[root@localhost ltp]# ./runltp -f cpuhotplug
- OS Version: RHEL 5.4
- Automake version:
[root@localhost ~]# automake --version
automake (GNU automake) 1.9.6
Written by Tom Tromey <tromey@redhat.com>.
Autoconf version:
[root@localhost ~]# autoconf --version
autoconf (GNU Autoconf) 2.59
Written by David J. MacKenzie and Akim Demaille.
- Arch: x86_64
I was able to run the same test w/o any issues with
ltp-full-20090731.tgz, which I "think" was the
last drop which would compile and install in the same location. Even in
the current case, I was able
to run the test only after I copied all folders from
/root/ltp-full-20100228/testcases to /opt/ltp/testcases.
Regards,
Shwetabh
On 3/3/2010 6:13 PM, Rishikesh K Rajak wrote:
> On Wed, Mar 03, 2010 at 04:05:43PM +0530, Shwetabh wrote:
>
>> Hi,
>>
>>
> Hi Shwetabh,
>
> Few queries:
> - Tell us the complete steps of execution/compiling
> - OS version ?
> - automake& autoconf version ?
> - Arch ?
>
> Thanks
> -Rishi
>
>
>> In recent ltp releases, I see quite a few test cases breaking since
>> their required tools
>> are not being copied over to /opt/ltp/testcases/. I believe this
>> behaviour started since
>> ltp started compiling and copying the files to /opt/ltp. Here is an example:
>>
>> ----<<snip>>-----------
>> remove test cases which require the block device.
>> You can specify it with option -b
>> COMMAND: /opt/ltp/bin/ltp-pan -e -S -a 27204 -n 27204 -p -f
>> /tmp/ltp-gcfmm27210/alltests -l
>> /opt/ltp/results/LTP_RUN_ON-2010_Mar_02-22h_24m_38s.log -C
>> /opt/ltp/output/LTP_RUN_ON-2010_Mar_02-22h_24m_38s.failed
>> LOG File: /opt/ltp/results/LTP_RUN_ON-2010_Mar_02-22h_24m_38s.log
>> FAILED COMMAND File:
>> /opt/ltp/output/LTP_RUN_ON-2010_Mar_02-22h_24m_38s.failed
>> Running tests.......
>> <<<test_start>>>
>> tag=CPUHOTPLUG stime=1267586681
>> cmdline="(cd $LTPROOT/testcases/kernel/hotplug/cpu_hotplug/; ./runtests.sh)"
>> contacts=""
>> analysis=exit
>> <<<test_output>>>
>> incrementing stop
>> sh: line 0: cd: /opt/ltp/testcases/kernel/hotplug/cpu_hotplug/: No such
>> file or directory
>> sh: ./runtests.sh: No such file or directory
>> <<<execution_status>>>
>> initiation_status="ok"
>> duration=0 termination_type=exited termination_id=127 corefile=no
>> cutime=0 cstime=0
>> <<<test_end>>>
>> INFO: ltp-pan reported some tests FAIL
>> LTP Version: LTP-20100228
>>
>> ###############################################################"
>>
>> Done executing testcases."
>> LTP Version: LTP-20100228
>> ###############################################################"
>>
>> [root@localhost runtest]# cd /opt/ltp/testcases/
>> [root@localhost testcases]# ls
>> bin data
>> [root@localhost testcases]# pwd
>> /opt/ltp/testcases
>> [root@localhost testcases]# ls -l
>> total 76
>> drwxr-xr-x 7 root root 69632 Mar 2 22:24 bin
>> drwxr-xr-x 2 root root 4096 Mar 2 22:19 data
>>
>> --------------------
>>
>> Please advice if I am doing something wrong here. Do I manually have to
>> copy the tools from tarballs' testcases/kernel directory?
>> If so, shouldn't this be done by make install?
>>
>> --
>> Regards,
>> Shwetabh
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>>
>
------------------------------------------------------------------------------
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-03 13:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 10:35 [LTP] Missing test tools in recent ltp builds Shwetabh
2010-03-03 12:41 ` Garrett Cooper
2010-03-03 12:43 ` Rishikesh K Rajak
2010-03-03 13:02 ` Shwetabh [this message]
2010-03-03 17:00 ` Maxin John
2010-03-03 23:16 ` Garrett Cooper
2010-03-04 6:45 ` Rishikesh K Rajak
2010-03-04 6:50 ` Garrett Cooper
2010-03-04 7:22 ` Shwetabh
2010-03-04 13:05 ` Maxin John
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=4B8E5DF3.7090502@calsoftinc.com \
--to=shwetabh.goel@calsoftinc.com \
--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 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.