From: Mark Wielaard <mark@klomp.org>
To: Christophe Lyon <christophe.lyon@arm.com>
Cc: Matthias Klose <matthias.klose@canonical.com>,
Nick Clifton <nickc@redhat.com>,
binutils@sourceware.org, buildbot@sourceware.org
Subject: Re: The 2.40 branch has been created
Date: Wed, 4 Jan 2023 01:35:57 +0100 [thread overview]
Message-ID: <20230104003557.GB9735@gnu.wildebeest.org> (raw)
In-Reply-To: <2351b01b-ace6-3028-ece5-0f47caf21950@arm.com>
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
Hi Christophe,
On Tue, Jan 03, 2023 at 06:29:30PM +0100, Christophe Lyon wrote:
> Actually we have:
> armhf-ubuntu20_04 and armhf-ubuntu22_04 to build GDB and
> ubuntu22_04-armhf to build GCC
>
> The containers we use to build GDB have less cores than the ones we
> use for GCC. If we add binutils builders on the same workers as GDB,
> will they cooperate nicely (as in "do not compete for CPU", ie. be
> scheduled at different times)?
>
> If yes, maybe it makes sense to add binutils builders to:
> armhf-ubuntu20_04
> armhf-ubuntu22_04
> arm64-ubuntu20_04
> arm64-ubuntu22_04
>
> WDYT?
That makes sense. Yes, they will cooperate nicely because the workers
all have max_builds=1. So if there are multiple builds that could use
the same worker they will just wait in the pending queue.
I'll push the following to try the new builders.
Thanks,
Mark
[-- Attachment #2: 0001-Add-binutils-ubuntu20_04-and-ubuntu22_04-armhf-and-a.patch --]
[-- Type: text/plain, Size: 2566 bytes --]
From e125fa6b21d87c8bb39649299762cdfbafe0282e Mon Sep 17 00:00:00 2001
From: Mark Wielaard <mark@klomp.org>
Date: Wed, 4 Jan 2023 01:16:18 +0100
Subject: [PATCH] Add binutils ubuntu20_04 and ubuntu22_04 armhf and arm64
builders
---
builder/master.cfg | 34 +++++++++++++++++++++++++++++++++-
1 file changed, 33 insertions(+), 1 deletion(-)
diff --git a/builder/master.cfg b/builder/master.cfg
index 8a66ae8..b16bb29 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -702,7 +702,11 @@ binutils_scheduler = schedulers.SingleBranchScheduler(
"binutils-debian-i386",
"binutils-fedora-ppc64le",
"binutils-opensusetw-x86_64",
- "binutils-opensuseleap-x86_64"])
+ "binutils-opensuseleap-x86_64",
+ "binutils-ubuntu20_04-armhf",
+ "binutils-ubuntu22_04-armhf",
+ "binutils-ubuntu20_04-arm64",
+ "binutils-ubuntu22_04-arm64"])
c['schedulers'].append(binutils_scheduler)
binutils_try_scheduler = schedulers.AnyBranchScheduler(
@@ -2331,6 +2335,34 @@ binutils_opensuseleap_x86_64_builder = util.BuilderConfig(
factory=binutils_factory)
c['builders'].append(binutils_opensuseleap_x86_64_builder)
+binutils_ubuntu20_04_armhf_builder = util.BuilderConfig(
+ name="binutils-ubuntu20_04-armhf",
+ workernames=["armhf-ubuntu20_04"],
+ tags=["binutils", "armhf", "ubuntu"],
+ factory=binutils_factory)
+c['builders'].append(binutils_ubuntu20_04_armhf_builder)
+
+binutils_ubuntu22_04_armhf_builder = util.BuilderConfig(
+ name="binutils-ubuntu22_04-armhf",
+ workernames=["armhf-ubuntu22_04"],
+ tags=["binutils", "armhf", "ubuntu"],
+ factory=binutils_factory)
+c['builders'].append(binutils_ubuntu22_04_armhf_builder)
+
+binutils_ubuntu20_04_arm64_builder = util.BuilderConfig(
+ name="binutils-ubuntu20_04-arm64",
+ workernames=["arm64-ubuntu20_04"],
+ tags=["binutils", "arm64", "ubuntu"],
+ factory=binutils_factory)
+c['builders'].append(binutils_ubuntu20_04_arm64_builder)
+
+binutils_ubuntu22_04_arm64_builder = util.BuilderConfig(
+ name="binutils-ubuntu22_04-arm64",
+ workernames=["arm64-ubuntu22_04"],
+ tags=["binutils", "arm64", "ubuntu"],
+ factory=binutils_factory)
+c['builders'].append(binutils_ubuntu22_04_arm64_builder)
+
binutils_rawhide_x86_64_builder = util.BuilderConfig(
name="binutils-rawhide-x86_64",
properties={'container-file':
--
2.31.1
next parent reply other threads:[~2023-01-04 0:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87mt739186.fsf@redhat.com>
[not found] ` <35a47bed-36af-6f8a-55a6-9cef247f9840@canonical.com>
[not found] ` <e6fcc285-becc-5816-db4a-36e37e8c08cd@arm.com>
[not found] ` <20230102230528.GA6490@gnu.wildebeest.org>
[not found] ` <2351b01b-ace6-3028-ece5-0f47caf21950@arm.com>
2023-01-04 0:35 ` Mark Wielaard [this message]
2023-01-04 10:31 ` Christophe Lyon
2023-01-04 11:07 ` 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=20230104003557.GB9735@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=binutils@sourceware.org \
--cc=buildbot@sourceware.org \
--cc=christophe.lyon@arm.com \
--cc=matthias.klose@canonical.com \
--cc=nickc@redhat.com \
/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).