From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [Automated-testing] [PATCH v2 1/1] doc: Add supported distros (kernel, libc, toolchain)
Date: Tue, 18 May 2021 21:13:14 +0200 [thread overview]
Message-ID: <YKQRyk/6SNiqUryH@pevik> (raw)
In-Reply-To: <YKP+KakyxIuGc/fo@yuki>
Hi Cyril,
> > +1. Build testing with Travis CI
> > +-------------------------------
> > +
> > +We test master branch in https://travis-ci.org/github/linux-test-project/ltp/builds[travis CI]
> > +to ensure LTP builds on various distributions including old, current and bleeding edge.
> > +We test both gcc and clang toolchains, various arch with cross-compilation.
> ^
> This should be plural
> so 'archs' I guess
+1
> > +For list of tested distros see
> > +https://github.com/linux-test-project/ltp/blob/master/.travis.yml[.travis.yml].
> > +
> > +
> > +NOTE: Travis does only build testing, passing the CI means only that the
> > + test compiles fine on variety of different distributions and releases.
> > + Also it uses the latest distribution image of a particular release.
> ^
> Travis also uses...
+1
> > +1.1 Oldest tested distributions
> > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > +
> > +[align="center",options="header"]
> > +|==============================================================
> > +| Distro | kernel | glibc | gcc | clang
> > +| CentOS 7 | 3.10 | 2.17 | 4.8.5 | -
> > +| Ubuntu 16.04 LTS xenial | 4.4 | 2.23 | 5.3.1 | -
> > +| Debian 9 stretch (oldstable) | 4.9.30 | 2.24 | 6.3.0 | 3.8
> > +|==============================================================
> > +
> > +Older distributions are not officially supported, which means that it
> > +may or may not work. It all depends on your luck. It should be possible
> > +to compile latest LTP even on slightly older distributions than we
> > +support with a few manual tweaks, e.g. disabling manually tests for
> > +newly added syscalls manually, etc. Trivial fixes/workarounds may be accepted,
> ^
> This 'manually' is redundant and should be removed.
+1
> > +but users are encouraged to move to a newer distro.
> > +
> > +If latest LTP cannot be compiled even with some amount of workarounds,
> > +you may result to older LTP releases, however these are _not_ supported
> > +in any way. Also if you are trying to run LTP on more than 10 years old
> > +distribution you may as well reconsider you life choices.
> So in the end you haven't changed this for the nicer version I've
> proposed?
I decided to keep it. We're saying similar thing in previous paragraph
("but users are encouraged to move to a newer distro") and it's actually the
truth (life choice to maintain ancient version). But feel free to suggest
further improvements over these 2 paragraphs.
Kind regards,
Petr
next prev parent reply other threads:[~2021-05-18 19:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 17:30 [LTP] [PATCH v2 1/1] doc: Add supported distros (kernel, libc, toolchain) Petr Vorel
2021-05-18 17:49 ` Cyril Hrubis
2021-05-18 19:13 ` Petr Vorel [this message]
2021-05-19 8:52 ` [LTP] [Automated-testing] " Cyril Hrubis
2021-05-19 11:24 ` Petr Vorel
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=YKQRyk/6SNiqUryH@pevik \
--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