From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [Automated-testing] [RFC PATCH 1/1] doc: Add supported kernel, libc versions
Date: Fri, 14 May 2021 17:06:53 +0200 [thread overview]
Message-ID: <YJ6SDSAsLoXHgnOc@pevik> (raw)
In-Reply-To: <YJ6A0gcR9L+P9IXm@yuki>
Hi Cyril,
> Hi!
> > +Supported kernel, libc, toolchain versions
> > +==========================================
> > +
> > +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.
> > +
> > +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.
> > +
> > +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
> > +|==============================================================
> > +
> > +For older versions please use https://github.com/linux-test-project/ltp/releases[older LTP releases].
> I'm not sure that this is a good suggestion.
> I would write something as:
> 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.
> 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.
+1 (although not sure about the latest sentence :))
> > +1.2 Supported architectures
> ^
> Tested?
+1
> We do support more than we test, right?
> > +~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > +
> > +[align="center",options="header"]
> > +|==================================
> > +| arch | build
> > +| x86_64 | native
> > +| x86 emulation | native
> > +| aarch64 | cross compilation
> > +| ppc64le | cross compilation
> > +| s390x | cross compilation
> > +|==================================
> > +
> > +1.3 Supported libc
> > +~~~~~~~~~~~~~~~~~~
> > +
> > +Targeted libc is https://www.gnu.org/software/libc/[GNU C Library (glibc)].
> > +
> > +https://uclibc-ng.org/[uClibc-ng] is not being tested should work as well as it
> > +attempt to maintain a glibc compatible interface
> > +(older https://www.uclibc.org/[uClibc] might have problems).
> > +
> > +https://musl.libc.org/[musl] is not yet supported
> ^
> fully?
+1
> > +(see https://github.com/linux-test-project/ltp/blob/master/travis/alpine.sh[travis script]
> > +for list of files which need to be deleted in order to compile under musl).
> > +
> > +For bionic libc please (Android) use https://android.googlesource.com/platform/external/ltp/[AOSP fork].
> Thanks a lot for starting this.
Thanks a lot for all the feedback, I'll take it all for v2.
It'd be nice to get it merged before the release.
Kind regards,
Petr
next prev parent reply other threads:[~2021-05-14 15:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 13:26 [LTP] [RFC PATCH 1/1] doc: Add supported kernel, libc versions Petr Vorel
2021-05-14 13:53 ` Cyril Hrubis
2021-05-14 15:06 ` Petr Vorel [this message]
2021-05-17 13:56 ` [LTP] [Automated-testing] " Cyril Hrubis
2021-05-18 8:29 ` Li Wang
2021-05-17 5:55 ` [LTP] " Jan Stancek
2021-05-17 6:42 ` Petr Vorel
2021-05-17 5:49 ` xuyang2018.jy
2021-05-17 6:50 ` 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=YJ6SDSAsLoXHgnOc@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