From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: Li Wang <liwang@redhat.com>, Petr Vorel <pvorel@suse.cz>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] New LTP documentation!
Date: Fri, 12 Apr 2024 10:34:13 +0200 [thread overview]
Message-ID: <8f9af233-4614-4f34-97fd-dd6728e6d893@suse.com> (raw)
In-Reply-To: <CAEemH2e7GAQmdkcu0p3p=4Hequ4nck2+ECeSfMYpXSpvKhqsDg@mail.gmail.com>
Hi,
On 4/11/24 11:00, Li Wang wrote:
> Hi Petr,
>
> On Wed, Apr 10, 2024 at 6:12 PM Petr Vorel <pvorel@suse.cz> wrote:
>
> 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?
>
>
> Yes, I did but only checked on RHEL-7.9 with x86_64 and s390x
> (compile & execution well) last time.
>
> After rebuilding the latest branch on all arches, I found the rest
> arches have
> problems in compiling (forgive me careless last time).
>
> Now I am hesitant to fix the error or raise the baseline to RHEL8.3.
> (I talked to colleagues and got to know they always chose to use fixed
> versions of LTP when <=RHEL8.2).
>
>
> ---------------------
> # 3.10.0-1136.el7.ppc64le
>
> # glibc-2.17-316.el7.ppc64le
>
> In file included from /usr/include/termios.h:40:0,
> from /usr/include/bits/ioctl-types.h:5,
> from /usr/include/sys/ioctl.h:29,
> from ../../../../include/lapi/ioctl.h:11,
> from ioctl02.c:31:
> /usr/include/bits/termios.h:33:8: error: redefinition of ‘struct termios’
> struct termios {
> ^
> In file included from ioctl02.c:29:0:
> /usr/include/asm/termbits.h:22:8: note: originally defined here
> struct termios {
> ^
>
>
> @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.
>
Feel free, I think it's a good idea. At the moment there's just a short
comment about Github actions here:
https://linux-test-project.readthedocs.io/en/latest/developers/writing_tests.html#testing-builds-with-github-actions
>
> Kind regards,
> Petr
>
> > [1]
> https://ltp-acerv.readthedocs.io/en/latest/users/supported_systems.html
>
>
>
> --
> Regards,
> Li Wang
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2024-04-12 8:34 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
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 [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=8f9af233-4614-4f34-97fd-dd6728e6d893@suse.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=liwang@redhat.com \
--cc=pvorel@suse.cz \
/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