From: "Serhei Makarov" <serhei@serhei.io>
To: "Frank Ch. Eigler" <fche@elastic.org>, "Mark Wielaard" <mark@klomp.org>
Cc: buildbot@sourceware.org
Subject: Re: [PATCH] Add full roster of fedora/rhel/centos-stream stap workers and builders
Date: Tue, 23 Apr 2024 17:37:38 -0400 [thread overview]
Message-ID: <b7fd993d-7dd2-4008-92b9-b4532c1ffd86@app.fastmail.com> (raw)
In-Reply-To: <Zigm9u8pHnhMnTDi@elastic.org>
On Tue, Apr 23, 2024, at 5:24 PM, Frank Ch. Eigler wrote:
> Hi -
>
>> [...] Would it make sense to name "rawhide", "fedora-latest" and
>> "fedora-old-stable" or something like that? Then you don't have to
>> rename them every few months. [...]
>
> I was thinking about that too. OTOH:
>
> - Only downside seemed to be 6-monthly new worker additions
> - I couldn't think of any other downside in terms of storage or UI
> - This lets us keep these older workers as long as we like. (Heck,
> I'm still interested in fedora 30, which is the last one that had
> a 32-bit i686 kernel.)
Another option I was pondering on orthogonal lines
was workers that run an upstream kernel that can be rebuilt
and rebooted with older / newer versions as needed for particular
testsuite runs.
This is needed to make any kind of retrospective testing work properly
(since older versions of systemtap can only work with older kernels).
Though I might stick to experimenting with that on the non-public
buildbots.
next prev parent reply other threads:[~2024-04-23 21:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 20:56 Serhei Makarov
2024-04-23 21:12 ` Frank Ch. Eigler
2024-04-23 21:16 ` Serhei Makarov
2024-04-23 21:19 ` Mark Wielaard
2024-04-23 21:24 ` Frank Ch. Eigler
2024-04-23 21:37 ` Serhei Makarov [this message]
2024-04-23 21:44 ` Mark Wielaard
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=b7fd993d-7dd2-4008-92b9-b4532c1ffd86@app.fastmail.com \
--to=serhei@serhei.io \
--cc=buildbot@sourceware.org \
--cc=fche@elastic.org \
--cc=mark@klomp.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).