From: Mark Wielaard <mark@klomp.org>
To: buildbot@sourceware.org
Cc: Mark Wielaard <mark@klomp.org>
Subject: [COMMITTED] gdb-alma-x86_64 is no longer broken, add gdb-try-alma-x86_64 back
Date: Mon, 22 Apr 2024 13:45:05 +0200 [thread overview]
Message-ID: <20240422114505.251183-1-mark@klomp.org> (raw)
---
builder/master.cfg | 17 +++++++++--------
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/builder/master.cfg b/builder/master.cfg
index 80f6270e2570..a372dae72143 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -961,6 +961,7 @@ gdb_try_scheduler = schedulers.AnyBranchScheduler(
onlyImportant=True,
reason="binutils-gdb project users try branch gdb files update",
builderNames=["gdb-try-fedora-x86_64",
+ "gdb-try-alma-x86_64",
"gdb-try-fedora-sanitize-x86_64",
"gdb-try-rawhide-x86_64",
"gdb-try-debian-testing-x86_64",
@@ -3210,17 +3211,17 @@ gdb_factory_sanitize.addStep(gdb_rm_step)
gdb_alma_x86_64_builder = util.BuilderConfig(
name="gdb-alma-x86_64",
workernames=["alma-x86_64"],
- tags=["gdb-broken", "alma", "x86_64"],
+ tags=["gdb", "alma", "x86_64"],
factory=gdb_no_sim_factory)
c['builders'].append(gdb_alma_x86_64_builder)
-#gdb_try_alma_x86_64_builder = util.BuilderConfig(
-# name="gdb-try-alma-x86_64",
-# collapseRequests=True,
-# workernames=["alma-x86_64"],
-# tags=["gdb-try", "alma", "x86_64"],
-# factory=gdb_factory)
-#c['builders'].append(gdb_try_alma_x86_64_builder)
+gdb_try_alma_x86_64_builder = util.BuilderConfig(
+ name="gdb-try-alma-x86_64",
+ collapseRequests=True,
+ workernames=["alma-x86_64"],
+ tags=["gdb-try", "alma", "x86_64"],
+ factory=gdb_factory)
+c['builders'].append(gdb_try_alma_x86_64_builder)
gdb_fedora_x86_64_builder = util.BuilderConfig(
name="gdb-fedora-x86_64",
--
2.39.3
reply other threads:[~2024-04-22 11:45 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=20240422114505.251183-1-mark@klomp.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.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).