hi,
"The Linux™ Test Project is a joint project started by SGI™ and maintained by IBM®, that has a goal to deliver test suites to the open source community that validate the reliability, robustness, and stability of Linux. The LTP testsuite contains a collection of tools for testing the Linux kernel and related features." -----------
In the week leading upto 6.4, Christoph Galuschka and I had started looking at how we might be able to integrate those tests into what we are doing. Since the 6.4 sprint kicked in, we resorted to just running the tests manually; Which worked well. However, I feel its worth putting these tests into the harness we have in place, and making sure they are run whenever we call for 'distro tests' or 'update tests'.
One option is to have the entire suite run as a single tests/r_ltp/ suiet under t_functional; the other is to either have its own suite, we can directly import from upstream, or have it be a part of the t_external/ test suite ( along with the likes of wordpress / drupal and other things ).
Thoughts ?
- KB
Hi Karanbir,
Thought I would forward this if you had not seen it!
easiest way to install hadoop on ubuntuhttp://www.linkedin.com/e/-cy1jqn-he9a9rve-44/vaq/207833953/988957/124906059/view_disc/?hs=false&tok=3kYF3Z2oX5HRE1
Successfully installed YARN (Hadoop 2.0.2-alpha) on ubuntu. Once ssh is setup the installation is straight forward unless you want to tweak the properties. I like the manual install as you don't know what these scripts are modifying on your system :)
By Neeraj Goswamy
*
*
HTH,
Bruce Basil Mathews
HP Cloud Services, DBaaS Architect
Hewlett-Packard Company
+1 760 961 7699 / Tel
+1 760 553 3197 / Mobile
bruce.mathews@hp.com / Email
12386 Pocomoke Road
Apple Valley, CA 92308
USA
HP Public Cloud Site: http://www.hpcloud.com
'All the world is a stage, and all the men and women in it, merely players'
Jaquis, As You Like It!
Please consider the environment before printing this email.
-----Original Message----- From: centos-devel-bounces@centos.org [mailto:centos-devel-bounces@centos.org] On Behalf Of Karanbir Singh Sent: Wednesday, March 13, 2013 10:16 AM To: centos-devel@centos.org Subject: [CentOS-devel] Adding Linux Test Project content to our tests
hi,
"The Linux(tm) Test Project is a joint project started by SGI(tm) and
maintained by IBM(r), that has a goal to deliver test suites to the open
source community that validate the reliability, robustness, and
stability of Linux. The LTP testsuite contains a collection of tools for
testing the Linux kernel and related features."
-----------
In the week leading upto 6.4, Christoph Galuschka and I had started
looking at how we might be able to integrate those tests into what we
are doing. Since the 6.4 sprint kicked in, we resorted to just running
the tests manually; Which worked well. However, I feel its worth putting
these tests into the harness we have in place, and making sure they are
run whenever we call for 'distro tests' or 'update tests'.
One option is to have the entire suite run as a single tests/r_ltp/
suiet under t_functional; the other is to either have its own suite, we
can directly import from upstream, or have it be a part of the
t_external/ test suite ( along with the likes of wordpress / drupal and
other things ).
Thoughts ?
- KB
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
hi,
"The Linux™ Test Project is a joint project started by SGI™ and
maintained by IBM®, that has a goal to deliver test suites to the open
source community that validate the reliability, robustness, and
stability of Linux. The LTP testsuite contains a collection of tools for
testing the Linux kernel and related features."
In the week leading upto 6.4, Christoph Galuschka and I had started
looking at how we might be able to integrate those tests into what we
are doing. Since the 6.4 sprint kicked in, we resorted to just running
the tests manually; Which worked well. However, I feel its worth putting
these tests into the harness we have in place, and making sure they are
run whenever we call for 'distro tests' or 'update tests'.
One option is to have the entire suite run as a single tests/r_ltp/
suiet under t_functional; the other is to either have its own suite, we
can directly import from upstream, or have it be a part of the
t_external/ test suite ( along with the likes of wordpress / drupal and
other things ).
Thoughts ?
- KB
I would suggest to let LTP have its own (= t_external) suite. I think it would get less udpates than t_functional (and wouldn't need a testrun every time t_functional gets a new test), and running the LTP-tests within t_functional would increase the time needed by about 30 mins.
cheers Christoph
On 03/14/2013 11:47 AM, Christoph Galuschka wrote:
I would suggest to let LTP have its own (= t_external) suite. I think it would get less udpates than t_functional (and wouldn't need a testrun every time t_functional gets a new test), and running the LTP-tests within t_functional would increase the time needed by about 30 mins.
the t_external suite would be a place to host all external apps and tests, so are you saying we should have one dedicated for ltp or are you saying lets put it in t_external/
- KB
Am 14.03.2013 19:32, schrieb Karanbir Singh:
On 03/14/2013 11:47 AM, Christoph Galuschka wrote:
I would suggest to let LTP have its own (= t_external) suite. I think it would get less udpates than t_functional (and wouldn't need a testrun every time t_functional gets a new test), and running the LTP-tests within t_functional would increase the time needed by about 30 mins.
the t_external suite would be a place to host all external apps and tests, so are you saying we should have one dedicated for ltp or are you saying lets put it in t_external/
- KB
i tend to say lets have a dedicated one - t_ltp maybe
Christoph
-
Christoph Galuschka -
Karanbir Singh -
Mathews, Bruce