public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@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: Fri, 21 Dec 2018 16:00:16 +0100	[thread overview]
Message-ID: <20181221150016.GC27446@dell5510> (raw)
In-Reply-To: <CADdDZRnSugmfoyv1Mpt-HBrMVP5mD7Y4g3wA1cB3yaTPoeoGAg@mail.gmail.com>

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

  reply	other threads:[~2018-12-21 15:00 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 [this message]
2019-01-03 10:42 ` Cyril Hrubis

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=20181221150016.GC27446@dell5510 \
    --to=pvorel@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