public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: buildbot@sourceware.org
Subject: Re: Builder credentials request for Gentoo/sparc
Date: Fri, 13 Jan 2023 20:46:38 +0000	[thread overview]
Message-ID: <DF9F5B88-76A4-429D-B512-E7525BD5B15A@gentoo.org> (raw)
In-Reply-To: <Y8HCCMlMcO4t/6HL@elastic.org>

[-- Attachment #1: Type: text/plain, Size: 830 bytes --]



> On 13 Jan 2023, at 20:41, Frank Ch. Eigler <fche@elastic.org> wrote:
> 
> Hi -
> 
>> As discussed on #overseers, I'd like to start off with some easy
>> builds with a Buildbot on our beefy sparc machine in Gentoo.
> 
> Nice.
> 
>> For now, let's say normal core count should be 8, and bursts of 16,
>> but we can crank that up significantly later. We'll start with just
>> bzip2.  It's okay to do 3-4 builds at a time. Again, we can probably
>> crank that up later.
> 
> bzip2 will produce approximately zero traffic, never mind 3-4 at a
> time.  Check out https://builder.sourceware.org/buildbot/#/ for the
> projects that are producing lots of buildbot traffic, and maybe choose
> one or more of those.

Oops. I was trying to avoid bothering people if there are failures
at first :)

Let's do binutils, gdb, bzip2.

Thanks!

[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]

  reply	other threads:[~2023-01-13 20:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13 20:17 Sam James
2023-01-13 20:41 ` Frank Ch. Eigler
2023-01-13 20:46   ` Sam James [this message]
2023-01-15 15:46   ` 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=DF9F5B88-76A4-429D-B512-E7525BD5B15A@gentoo.org \
    --to=sam@gentoo.org \
    --cc=buildbot@sourceware.org \
    --cc=fche@elastic.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).