From: Shwetabh <shwetabh.goel@calsoftinc.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: "ltp-list@lists.sourceforge.net" <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] Missing test tools in recent ltp builds
Date: Thu, 04 Mar 2010 12:52:32 +0530 [thread overview]
Message-ID: <4B8F5FB8.103@calsoftinc.com> (raw)
In-Reply-To: <364299f41003032250i78c201fesc5ce55d6d2c2794f@mail.gmail.com>
Hi Garett,
There is one possible problem with the current solution provided by
Maxin. The patch takes care
only of cpuhotplug tests. However, judging by the number of files that
are missing in /opt/ltp/testcases,
it is quite possible that many other tests might have been broken. So,
perhaps a generic solution to this
problem would be to modify the Makefile to ensure that it copies all
directories from ltp-full-20100228/testcases/
to /opt/ltp/testcases/.
Here is a listing of files in both directories after an installation has
been performed:
----Installation Directory------
[root@localhost ~]# ls -l /root/ltp-full-20100228/testcases/
total 56
drwxrwxr-x 3 500 500 4096 Mar 1 09:58 ballista
drwxrwxr-x 15 500 500 4096 Mar 1 09:58 commands
drwxrwxr-x 6 500 500 4096 Mar 1 09:58 DOTS
drwxrwxr-x 5 500 500 4096 Mar 1 09:58 kdump
drwxrwxr-x 21 500 500 4096 Mar 1 09:58 kernel
drwxrwxr-x 2 500 500 4096 Mar 1 09:58 lib
-rw-rw-r-- 1 500 500 1381 Mar 1 09:58 Makefile
drwxrwxr-x 9 500 500 4096 Mar 1 09:58 mce-test
drwxrwxr-x 6 500 500 4096 Mar 1 09:58 misc
drwxrwxr-x 18 500 500 4096 Mar 3 19:00 network
drwxrwxr-x 15 500 500 4096 Mar 1 09:58 open_hpi_testsuite
drwxrwxr-x 7 500 500 4096 Mar 1 09:58 open_posix_testsuite
drwxrwxr-x 5 500 500 4096 Mar 1 09:58 pounder21
drwxrwxr-x 13 500 500 4096 Mar 3 18:51 realtime
---------------------------------
------Target Directory-----------
[root@localhost ~]# ls -l /opt/ltp/testcases/
total 76
drwxr-xr-x 7 root root 69632 Mar 3 19:01 bin
drwxr-xr-x 2 root root 4096 Mar 3 19:01 data
---------------------------------
Regards,
Shwetabh
On 3/4/2010 12:20 PM, Garrett Cooper wrote:
> On Wed, Mar 3, 2010 at 10:45 PM, Rishikesh K Rajak
> <risrajak@linux.vnet.ibm.com> wrote:
>
>> On Wed, Mar 03, 2010 at 03:16:47PM -0800, Garrett Cooper wrote:
>>
>>> On Mar 3, 2010, at 9:00 AM, Maxin John<maxin.john@gmail.com> wrote:
>>>
>>>
>>>> Hi Shwetabh,
>>>>
>>>>
>>>>> 3. Went to /opt/ltp directory and tried to execute cpuhotplug test:
>>>>> [root@localhost ~]# cd /opt/ltp/
>>>>> [root@localhost ltp]# ./runltp -f cpuhotplug
>>>>>
>>>>>
>>>> Please find attached the quick 'n' dirty patch
>>>> (cpu_hotplugin_makefile.patch) to execute cpuhotplugin test.
>>>> I have observed that the 'hotplug' directory is not included in
>>>> "testcases/kernel/Makefile". I have also
>>>> created a Makefile in 'hotplug/cpu_hotplug' directory.
>>>>
>>>> After applying this patch, I have followed the usual ./configure;
>>>> make; sudo make install steps and executed
>>>> the cpuhotplug test and observed the below given output . It seems
>>>> like the test execution is "not so good" in
>>>> my machine. Your mileage may vary.
>>>>
>>>> Garret,Rishi, please review the patch and let me know your comments.
>>>>
>>>> Signed-off-by: Maxin B. John<maxin.john@gmail.com>
>>>>
>>> It looks better but it's going to need a minor amount of fudging in
>>> the scripts to source the appropriate scripts to execute cpuhotplug's
>>> tests... I'll pick this up tomorrow if it's not done by then...
>>>
>> Yes it looks better, i have tested it and true there are still some
>> problem with testcase, can you look very closely and try to find the
>> root cause for that ? Since this patch is important to run cpuhotplug
>> testcases, i have included this to master branch.
>>
> I'm not arguing that it's a good step towards getting the task
> solved; I'm arguing that the change wasn't complete. I'm cleaning it
> up right now...
> Thanks,
> -Garrett
>
>
------------------------------------------------------------------------------
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-04 7:22 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
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 [this message]
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=4B8F5FB8.103@calsoftinc.com \
--to=shwetabh.goel@calsoftinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox