From: Mark Wielaard <mark@klomp.org>
To: buildbot@sourceware.org
Cc: Sam James <sam@gentoo.org>, Mark Wielaard <mark@klomp.org>
Subject: [PATCH] Add gdb try and ci builder on gentoo-sparc
Date: Fri, 13 Jan 2023 22:58:11 +0100 [thread overview]
Message-ID: <20230113215811.477630-1-mark@klomp.org> (raw)
---
builder/master.cfg | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/builder/master.cfg b/builder/master.cfg
index 6be5396..8789dd5 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -782,6 +782,7 @@ gdb_scheduler = schedulers.SingleBranchScheduler(
"gdb-debian-testing-x86_64",
"gdb-debian-armhf",
"gdb-fedora-arm64",
+ "gdb-gentoo-sparc",
"gdb-arm64-ubuntu20_04",
"gdb-arm64-ubuntu22_04",
"gdb-armhf-ubuntu20_04",
@@ -810,6 +811,7 @@ gdb_try_scheduler = schedulers.AnyBranchScheduler(
"gdb-try-rawhide-x86_64",
"gdb-try-debian-testing-x86_64",
"gdb-try-fedora-arm64",
+ "gdb-try-gentoo-sparc",
"gdb-try-debian-i386",
"gdb-try-fedora-s390x",
"gdb-try-fedora-ppc64le",
@@ -2682,6 +2684,20 @@ gdb_try_fedora_arm64_builder = util.BuilderConfig(
factory=gdb_factory)
c['builders'].append(gdb_try_fedora_arm64_builder)
+gdb_gentoo_sparc_builder = util.BuilderConfig(
+ name="gdb-gentoo-sparc",
+ workernames=["gentoo-sparc"],
+ tags=["gdb", "gentoo", "sparc"],
+ factory=gdb_factory)
+c['builders'].append(gdb_gentoo_sparc_builder)
+
+gdb_try_gentoo_sparc_builder = util.BuilderConfig(
+ name="gdb-try-gentoo-sparc",
+ workernames=["gentoo-sparc"],
+ tags=["gdb-try", "gentoo", "sparc"],
+ factory=gdb_factory)
+c['builders'].append(gdb_try_gentoo_sparc_builder)
+
gdb_debian_i386_builder = util.BuilderConfig(
name="gdb-debian-i386",
workernames=debian_i386_workers,
--
2.31.1
reply other threads:[~2023-01-13 21:58 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=20230113215811.477630-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).