From: Mark Wielaard <mark@klomp.org>
To: buildbot@sourceware.org
Cc: Sam James <sam@gentoo.org>, Mark Wielaard <mark@klomp.org>
Subject: [PATCH] Add gentoo-sparc-big worker using 32/64 cores.
Date: Sun, 29 Jan 2023 15:08:56 +0100 [thread overview]
Message-ID: <20230129140856.119797-1-mark@klomp.org> (raw)
---
buildbot.config.sample | 1 +
builder/master.cfg | 11 +++++++++++
2 files changed, 12 insertions(+)
diff --git a/buildbot.config.sample b/buildbot.config.sample
index 80ed109..d61fb56 100644
--- a/buildbot.config.sample
+++ b/buildbot.config.sample
@@ -24,6 +24,7 @@ ubuntu22_04-arm64=frob
ubuntu22_04-armhf=frob
fedora-arm64=frob
gentoo-sparc=frob
+gentoo-sparc-big=frob
# Users
bb_admin=frob
diff --git a/builder/master.cfg b/builder/master.cfg
index 6528fd5..82b9921 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -131,6 +131,10 @@ fedrawhide_x86_64_worker = worker.Worker("fedrawhide-x86_64",
notify_on_missing=['fche@elastic.org']);
c['workers'].append(fedrawhide_x86_64_worker)
+# 2 gentoo sparc workers, running on the same machine in different
+# containers. The big one does only one build at a time. Larger builds
+# are only put on the big worker to not hold up quicker/smaller builds.
+# Smaller builds can be done on either worker.
gentoo_sparc_worker = worker.Worker("gentoo-sparc",
getpw("gentoo-sparc"),
max_builds=3,
@@ -138,6 +142,13 @@ gentoo_sparc_worker = worker.Worker("gentoo-sparc",
notify_on_missing=['sam@gentoo.org']);
c['workers'].append(gentoo_sparc_worker)
+gentoo_sparc_big_worker = worker.Worker("gentoo-sparc-big",
+ getpw("gentoo-sparc-big"),
+ max_builds=3,
+ properties={'ncpus': 32, 'maxcpus': 64},
+ notify_on_missing=['sam@gentoo.org']);
+c['workers'].append(gentoo_sparc_big_worker)
+
# 3 (Fedora Core) VMs which can run container files
# 2 can do simultanious builds, and so have 2 latent workers with different
--
2.31.1
reply other threads:[~2023-01-29 14:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230129140856.119797-1-mark@klomp.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
--cc=sam@gentoo.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).