From: DJ Delorie <dj@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: carlos@redhat.com, libc-alpha@sourceware.org
Subject: Re: Buildbot improvements
Date: Thu, 15 Jul 2021 00:11:46 -0400 [thread overview]
Message-ID: <xnzguop665.fsf@greed.delorie.com> (raw)
In-Reply-To: <d17d0ff4-cf6c-8d01-a90d-f1e129e22ba8@linaro.org>
Adhemerval Zanella <adhemerval.zanella@linaro.org> writes:
> I take this builbot setup is used along with Fedora to stress both systems,
> but maybe it would better to use a more stable baseline to make it easier
> to reproduce. Either Fedora current or a way to download the required
> packages/tools.
I use the published registry.fedoraproject.org/fedora base container.
We chose to use the latest container for security reasons, to make sure
we had all the current security errata etc. It probably won't change
often enough to be an issue, but it means that I can't guarantee an
exact reproduction of a given trybot container.
Even if the containers were published, the trybot's container includes a
full copy of the glibc git tree at that moment, and we're hoping that
there will eventually be many trybots - not just mine - so consider the
cost of moving all that data around vs just running your own trybot ;-)
Note that I'm not defending my choice here, just explaining it. I'm
open to new ideas and tweaks.
next prev parent reply other threads:[~2021-07-15 4:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 18:18 Adhemerval Zanella
2021-07-13 19:15 ` DJ Delorie
2021-07-14 20:43 ` Carlos O'Donell
2021-07-14 21:10 ` DJ Delorie
2021-07-14 21:58 ` Adhemerval Zanella
2021-07-15 4:11 ` DJ Delorie [this message]
2021-07-15 12:24 ` Carlos O'Donell
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=xnzguop665.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.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).