From: Mark Wielaard <mark@klomp.org>
To: buildbot@sourceware.org
Cc: David Abdurachmanov <david.abdurachmanov@gmail.com>,
Mark Wielaard <mark@klomp.org>
Subject: [PATCH 3/4] Add gnupoke-ubuntu-riscv builder
Date: Sun, 31 Dec 2023 00:17:11 +0100 [thread overview]
Message-ID: <20231230231712.632110-4-mark@klomp.org> (raw)
In-Reply-To: <20231230231712.632110-1-mark@klomp.org>
---
builder/master.cfg | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/builder/master.cfg b/builder/master.cfg
index d97d62a..887aead 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -1015,6 +1015,7 @@ gnupoke_scheduler = schedulers.SingleBranchScheduler(
builderNames=["gnupoke-debian-testing-x86_64",
"gnupoke-debian-i386",
"gnupoke-gentoo-sparc",
+ "gnupoke-ubuntu-riscv",
"gnupoke-fedora-arm64"])
c['schedulers'].append(gnupoke_scheduler)
@@ -4621,6 +4622,13 @@ gnupoke_gentoo_space_builder = util.BuilderConfig(
factory=gnupoke_factory)
c['builders'].append(gnupoke_gentoo_space_builder)
+gnupoke_ubuntu_riscv_builder = util.BuilderConfig(
+ name="gnupoke-ubuntu-riscv",
+ tags=["gnupoke", "ubuntu", "riscv"],
+ workernames="starfive-riscv",
+ factory=gnupoke_factory)
+c['builders'].append(gnupoke_ubuntu_riscv_builder)
+
gnupoke_fedora_arm64_builder = util.BuilderConfig(
name="gnupoke-fedora-arm64",
tags=["gnupoke", "fedora", "arm64"],
--
2.39.3
next prev parent reply other threads:[~2023-12-30 23:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-30 23:17 Add more riscv builders for dwz, bzip2 and gnupoke Mark Wielaard
2023-12-30 23:17 ` [PATCH 1/4] Add dwz-ubuntu-riscv builder Mark Wielaard
2023-12-30 23:17 ` [PATCH 2/4] Add bzip2-ubuntu-riscv builder Mark Wielaard
2023-12-30 23:17 ` Mark Wielaard [this message]
2023-12-30 23:17 ` [PATCH 4/4] Add collapseRequests=True to all riscv builders 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=20231230231712.632110-4-mark@klomp.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
--cc=david.abdurachmanov@gmail.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).