public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] Should people be concerned if they run the tests on their work boxes and getting ltp in distributions.
Date: Thu, 3 Jan 2019 11:42:20 +0100	[thread overview]
Message-ID: <20190103104220.GB10514@rei.lan> (raw)
In-Reply-To: <CADdDZRnSugmfoyv1Mpt-HBrMVP5mD7Y4g3wA1cB3yaTPoeoGAg@mail.gmail.com>

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

      parent reply	other threads:[~2019-01-03 10:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 message]

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=20190103104220.GB10514@rei.lan \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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