public inbox for
 help / color / mirror / Atom feed
From: Szabolcs Nagy <>
To: Mark Wielaard <>
Cc:,,, Thomas Fitzsimmons <>,
Subject: Re: buildbot users try branch builders
Date: Tue, 21 Jun 2022 11:30:38 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

The 06/20/2022 12:48, Mark Wielaard wrote:
> The armhf and arm64 builders have left out for now since they are a
> bit too slow. We'll hopefully get a 8 core Ampare machine from the
> Oregon State University this week so we can also enable those arm
> builders.

what is the requirement for the machine? i have an aarch64 machine
for public gnu tools ci, and i can set up build slaves there if
there are instructions how to do it.

  reply	other threads:[~2022-06-21 10:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20 10:48 Mark Wielaard
2022-06-21 10:30 ` Szabolcs Nagy [this message]
2022-06-21 17:30   ` Mark Wielaard
2022-06-22  6:32 ` Jan Beulich
2022-06-22  7:30   ` Andreas Schwab
2022-06-22 10:51   ` Mark Wielaard
2022-06-22 11:04     ` Andreas Schwab
2022-07-04  6:39       ` Jan Beulich
2022-07-04 14:10         ` Andreas Schwab

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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).