public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Jan Stancek <jstancek@redhat.com>, Li Wang <liwang@redhat.com>
Cc: Ulrich Hecht <uli@kernel.org>,
	ltp@lists.linux.it, Richard Palethorpe <rpalethorpe@suse.com>,
	Martin Doucha <martin.doucha@suse.com>,
	automated-testing@lists.yoctoproject.org
Subject: Re: [LTP] [PATCH 0/2] Remove CentOS 7 support
Date: Wed, 1 Nov 2023 12:17:22 +0100	[thread overview]
Message-ID: <20231101111722.GB896131@pevik> (raw)
In-Reply-To: <CAASaF6yVnrBK0UCxj4HRbi_scm84KS5Jm_xi8rUEuXcZXo=rZQ@mail.gmail.com>

Hi all,

Note for myself: typo in subject s/ReAplace/Replace/

> > we recently had yet another regression on old CentOS 7 (kernel 3.10,
> > glibc 2.17, gcc 4.8.5 [1]. That brought me to the question if we still
> > want to support it.

> > Although we test in SUSE also very old SLES releases, these are tested
> > with older LTP releases. I suppose Red Hat does the same with RHEL
> > (Li, Jan, please correct me if not, or feel free to introduce another
> > CentOS version, as there will none with this patchset), thus why
> > pretend current LTP is useful on these old releases.

> Looking at internal LTP test wrapper, it's using older LTP release for RHEL7,
> so your assumption appears to be correct.


> > I wonder who is actually interested in keeping LTP compilable for CentOS 7.
> > According to distrowatch it EOL in 2024-06 [2], but does anybody even run new
> > LTP on it. If yes, please speak up, but I'd expect that person to
> > actually maintain CI failures.

> There's planned ELS until 2026, but I'd expect that continues using
> older LTP for tests.

@Li, Jan Could you please add your ABT or RBT?
Also, feel free to add quay.io/centos/centos:stream9 or rockylinux:9 or
rockylinux:8 or whatever makes sense to you. These are tested in
https://github.com/iputils/iputils/blob/master/.github/workflows/ci.yml
(it would have to be checked if ci/centos.sh needs be modified to support).

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  parent reply	other threads:[~2023-11-01 11:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25 14:01 [LTP] [PATCH 0/2] Remove CentOS 7 support Petr Vorel
2023-10-25 14:01 ` [LTP] [PATCH 1/2] CI: ReAplace CentOS 7 with openSUSE Leap 42.2, Ubuntu xenial Petr Vorel
2023-10-25 14:01 ` [LTP] [PATCH 2/2] doc/support: Update the latest tested distros Petr Vorel
2023-10-26  8:12 ` [LTP] [PATCH 0/2] Remove CentOS 7 support Jan Stancek
2023-10-26  8:21   ` Petr Vorel
2023-11-01 11:17   ` Petr Vorel [this message]
2023-11-01 12:28     ` Jan Stancek
2023-11-02  2:49       ` Li Wang
2023-11-02  3:01         ` Chao Ye

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=20231101111722.GB896131@pevik \
    --to=pvorel@suse.cz \
    --cc=automated-testing@lists.yoctoproject.org \
    --cc=jstancek@redhat.com \
    --cc=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    --cc=martin.doucha@suse.com \
    --cc=rpalethorpe@suse.com \
    --cc=uli@kernel.org \
    /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