From: Mark Wielaard <mark@klomp.org>
To: buildbot@sourceware.org
Cc: Thomas Fitzsimmons <fitzsim@fitzsim.org>, Mark Wielaard <mark@klomp.org>
Subject: [COMMITTED] Add collapseRequests for debian-ppc64 glibc, gdb, binutils and gccrust
Date: Tue, 16 Jan 2024 00:38:50 +0100 [thread overview]
Message-ID: <20240115233850.145583-1-mark@klomp.org> (raw)
There is only one debian-ppc64[be] builder which can get behind on
the bigger builds. Add collapseRequests=True to the builders to allow
it to catch up.
---
builder/master.cfg | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/builder/master.cfg b/builder/master.cfg
index 84a3b22..a31483d 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -2490,6 +2490,7 @@ gccrust_debian_ppc64_builder = util.BuilderConfig(
name="gccrust-debian-ppc64",
workernames=["debian-ppc64"],
tags=["gccrust", "debian", "ppc64"],
+ collapseRequests=True,
factory=gccrust_factory)
c['builders'].append(gccrust_debian_ppc64_builder)
@@ -2759,6 +2760,7 @@ binutils_debian_ppc64_builder = util.BuilderConfig(
name="binutils-debian-ppc64",
workernames=["debian-ppc64"],
tags=["binutils", "debian", "ppc64"],
+ collapseRequests=True,
factory=binutils_factory)
c['builders'].append(binutils_debian_ppc64_builder)
@@ -3234,6 +3236,7 @@ gdb_debian_ppc64_builder = util.BuilderConfig(
name="gdb-debian-ppc64",
workernames=["debian-ppc64"],
tags=["gdb", "debian", "ppc64"],
+ collapseRequests=True,
factory=gdb_factory)
c['builders'].append(gdb_debian_ppc64_builder)
@@ -3788,6 +3791,7 @@ glibc_debian_ppc64_builder = util.BuilderConfig(
name="glibc-debian-ppc64",
workernames=["debian-ppc64"],
tags=["glibc", "debian", "ppc64"],
+ collapseRequests=True,
factory=glibc_build_factory)
c['builders'].append(glibc_debian_ppc64_builder)
--
2.39.3
reply other threads:[~2024-01-15 23:39 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=20240115233850.145583-1-mark@klomp.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
--cc=fitzsim@fitzsim.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).