public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
* [LTP] Should people be concerned if they run the tests on their work boxes and getting ltp in distributions.
@ 2018-12-21  6:35 shirish =?unknown-8bit?b?4KS24KS/4KSw4KWA4KS3?=
  2018-12-21 15:00 ` Petr Vorel
  2019-01-03 10:42 ` Cyril Hrubis
  0 siblings, 2 replies; 3+ messages in thread
From: shirish =?unknown-8bit?b?4KS24KS/4KSw4KWA4KS3?= @ 2018-12-21  6:35 UTC (permalink / raw)
  To: ltp

Dear all,

First of all thank you for making this series of tests and also some
of the documentation you have made. Please CC me as I have disabled
mailing list simply because I cannot keep up with the deluge of mail
that arrives everyday.

Although one of the questions which probably should be part of the FAQ
is should there be any concerns in running the tests on your everyday
work machines ? I know that ideally it should be  run in  a lab but
what if you do not have acces to that sort of infrastructure ? Are
these any sort of good practises that people recommend to read through
before starting the tests ?

I was able to compile and install ltp to /opt/ltp successfully and
even run the version command, although found it a bit curious as to
why autotools is used instead of something like cmake which has more
readable human error output.

I also was wondering if there have been distributions which are either
using ltp as part of their test infrastructure or/and also building
binaries for their users .

-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [LTP] Should people be concerned if they run the tests on their work boxes and getting ltp in distributions.
  2018-12-21  6:35 [LTP] Should people be concerned if they run the tests on their work boxes and getting ltp in distributions shirish =?unknown-8bit?b?4KS24KS/4KSw4KWA4KS3?=
@ 2018-12-21 15:00 ` Petr Vorel
  2019-01-03 10:42 ` Cyril Hrubis
  1 sibling, 0 replies; 3+ messages in thread
From: Petr Vorel @ 2018-12-21 15:00 UTC (permalink / raw)
  To: ltp

Hi shirish,

> Although one of the questions which probably should be part of the FAQ
> is should there be any concerns in running the tests on your everyday
> work machines ? I know that ideally it should be  run in  a lab but
> what if you do not have acces to that sort of infrastructure ? Are
> these any sort of good practises that people recommend to read through
> before starting the tests ?
https://github.com/linux-test-project/ltp/blob/master/README.md#warning

> I was able to compile and install ltp to /opt/ltp successfully and
> even run the version command, although found it a bit curious as to
> why autotools is used instead of something like cmake which has more
> readable human error output.
IMHO while autotools have lots of disadvantages, they're better for use then
CMake (better for broken toolchain checks + we're not using C++, building only
on windows).

> I also was wondering if there have been distributions which are either
> using ltp as part of their test infrastructure or/and also building
> binaries for their users .
IMHO only embedded ones: buildroot [1], and Yocto/OpenEmbedded [2], android [3]
Gentoo had it [4], but removed it 2 years ago [5], also other distros had it
[6].  And QA teams in enterprise distros use it for testing (SLES, RHEL, Oracle
Linux, ...).  We don't expect it to be packaged in in normal distros, that's why
we have static libraries (easier to reinstall for embedded, although I wanted to
optionally build shred libraries instead) and use default PREFIX /opt.

Kind regards,
Petr

[1] https://git.busybox.net/buildroot/tree/package/ltp-testsuite
[2] http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-extended/ltp/
[3] https://android.googlesource.com/platform/external/ltp/
[4] https://gitweb.gentoo.org/repo/gentoo.git/tree/app-benchmarks/ltp?id=469b5b5fe0ed34052bafe67b3fc065468faeec3d
[5] https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=755e2e74b59343ea17fa6b7582ced53cd83dfd0f
[6] https://pkgs.org/download/ltp

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [LTP] Should people be concerned if they run the tests on their work boxes and getting ltp in distributions.
  2018-12-21  6:35 [LTP] Should people be concerned if they run the tests on their work boxes and getting ltp in distributions shirish =?unknown-8bit?b?4KS24KS/4KSw4KWA4KS3?=
  2018-12-21 15:00 ` Petr Vorel
@ 2019-01-03 10:42 ` Cyril Hrubis
  1 sibling, 0 replies; 3+ messages in thread
From: Cyril Hrubis @ 2019-01-03 10:42 UTC (permalink / raw)
  To: ltp

Hi!
> First of all thank you for making this series of tests and also some
> of the documentation you have made. Please CC me as I have disabled
> mailing list simply because I cannot keep up with the deluge of mail
> that arrives everyday.
> 
> Although one of the questions which probably should be part of the FAQ
> is should there be any concerns in running the tests on your everyday
> work machines ? I know that ideally it should be  run in  a lab but
> what if you do not have acces to that sort of infrastructure ? Are
> these any sort of good practises that people recommend to read through
> before starting the tests ?

It's directly in the README:

"
Warning!

Be careful with these tests!

Don't run them on production systems. Growfiles, doio, and iogen in
particular stress the I/O capabilities of systems and while they should
not cause problems on properly functioning systems, they are intended to
find (or cause) problems.
"

Generally it's quite likely that running whole run will crash your
system unless you have up-to-date system with latest fixes and even with
up to date system it's risky bussines.

You would be better off with running the tests in VM.

> I was able to compile and install ltp to /opt/ltp successfully and
> even run the version command, although found it a bit curious as to
> why autotools is used instead of something like cmake which has more
> readable human error output.

Well LTP is older than cmake and all the new fancy tools, at the time
LTP was founded autotools was likely only viable option. And it
continues to work fine, so there is no real reason for a change. We have
far to many more important tasks to work on.

> I also was wondering if there have been distributions which are either
> using ltp as part of their test infrastructure or/and also building
> binaries for their users .

Sure we are:

https://openqa.opensuse.org/tests/overview?distri=opensuse&version=Tumbleweed&build=20181231&groupid=32

And there is a little outdated version in buildservice:

https://build.opensuse.org/package/show/benchmark/ltp

You would be better of with manual compilation though, since this one is
too old to be really useful.


Or you can try my testing package, that more or less follow latest git:

https://build.opensuse.org/package/show/home:metan/ltp


-- 
Cyril Hrubis
chrubis@suse.cz

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2019-01-03 10:42 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-12-21  6:35 [LTP] Should people be concerned if they run the tests on their work boxes and getting ltp in distributions shirish =?unknown-8bit?b?4KS24KS/4KSw4KWA4KS3?=
2018-12-21 15:00 ` Petr Vorel
2019-01-03 10:42 ` Cyril Hrubis

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox