From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] New LTP documentation!
Date: Wed, 10 Apr 2024 12:12:25 +0200 [thread overview]
Message-ID: <20240410101225.GA187895@pevik> (raw)
In-Reply-To: <CAEemH2eDT6gN3hw=Lz2qgnwFnnHmNYai9tqbKduSkcWfNjpERQ@mail.gmail.com>
Hi all,
> Hi Andrea,
> On Mon, Mar 18, 2024 at 8:41 PM Andrea Cervesato via ltp <ltp@lists.linux.it>
> wrote:
> > Hello everyone,
> > as already mentioned in the monthly LTP meeting, Linux Test Project
> > lacks of a nice and clean documentation that can be easily accessed by
> > users, developers and maintainers.
> > The current LTP documentation is also not matching with our expectancy
> > towards the entire project, which is has been heavily refactored and it
> > has changed in the past years, providing a higher quality code and new
> > testing features.
> > For this reasons, we think it's time to move forward and to start
> > working on documentation, helping people to use, to develop and to
> > maintain LTP in an easier way, increasing quality of the overall project
> > and to call more developers in the community.
> > I started to work on documentation refactoring, re-organizing the
> > overall structure. The first prototype can be found here:
> > https://ltp-acerv.readthedocs.io/en/latest/index.html
> Looks great! Thanks for bringing this.
> And I just tried that the latest LTP compiled & executed succeed on
> RHEL-7.9.
> Can you update the "Oldest tested distributions" [1] part by adding:
> RHEL-7.9 Maipo (Distro) 3.10 (kernel) 4.8.5(gcc) 2.17(glibc) -(clang)
Although in the original docs, the table was not under section "Build testing
with GitHub Actions", I assumed it's clear we talk about GitHub Actions testing.
That's why I put there only distros we actually have in .github/workflows/ci.yml
and not e.g. SLE12-SP2 which we test with latest LTP release.
I actually find useful to stand which distros we test privately, but this info
should be obvious (either add a column "CI", where would be "GitHub Actions" or
"RHEL private CI" or whatever.
@Li Andrea put there as new info: "Minimal supported kernel version is 3.10."
which is not in old docs. Do you really test RHEL-7.9 (3.10 based) with the
latest LTP release?
@Yang Xu I found you removed fallbacks up to kernel 3.10:
06ada0329 ("Remove old kernel version check when using min_kver under 3.10")
862d94c45 ("Remove old kernel version check when using tst_kvercmp under 3.10")
971828c00 ("shell: Remove old kernel version check below 3.10")
Hopefully I haven't overlook anything.
@Andrea: Also, I would prefer to put back paragraph "1. Build testing with
GitHub Actions". I'll send a patch, to force myself to learn building new docs.
Kind regards,
Petr
> [1] https://ltp-acerv.readthedocs.io/en/latest/users/supported_systems.html
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-04-10 10:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 12:41 [LTP] New LTP documentation! Andrea Cervesato via ltp
2024-03-18 17:01 ` Petr Vorel
2024-03-19 8:06 ` Andrea Cervesato via ltp
2024-03-19 10:33 ` Cyril Hrubis
2024-03-19 12:28 ` Li Wang
2024-03-19 14:40 ` Cyril Hrubis
2024-03-20 2:52 ` Li Wang
2024-03-20 7:44 ` Andrea Cervesato via ltp
2024-03-20 7:48 ` Li Wang
2024-04-10 10:12 ` Petr Vorel [this message]
2024-04-11 9:00 ` Li Wang
2024-04-11 13:38 ` Petr Vorel
2024-04-13 4:03 ` Li Wang
2024-04-12 8:34 ` Andrea Cervesato via ltp
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=20240410101225.GA187895@pevik \
--to=pvorel@suse.cz \
--cc=liwang@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).