public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: buildbot@sourceware.org
Cc: David Abdurachmanov <david.abdurachmanov@gmail.com>,
	Mark Wielaard <mark@klomp.org>
Subject: [COMMITTED] Add glibc-ubuntu-riscv builder
Date: Fri, 23 Feb 2024 00:54:08 +0100	[thread overview]
Message-ID: <20240222235408.2220719-1-mark@klomp.org> (raw)

The glibc build takes a long time ~30 minutes for make -j4
and ~2.5 hours for make check -j4. But the result is pretty good:

                === Summary of results ===
      4 FAIL
   4698 PASS
     21 UNSUPPORTED
     16 XFAIL
      2 XPASS

Since it takes such a long time glibc builds for riscv are done
one one specific board and the builds are collapsed (we won't try
a build for every single commit).
---
 builder/master.cfg | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/builder/master.cfg b/builder/master.cfg
index 5f21a2b..84b7b3d 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -1040,6 +1040,7 @@ glibc_build_scheduler = schedulers.AnyBranchScheduler(
                       "glibc-fedora-s390x",
                       "glibc-debian-ppc64",
                       "glibc-fedora-ppc64le",
+                      "glibc-ubuntu-riscv",
                       "glibc-gentoo-sparc"])
 c['schedulers'].append(glibc_build_scheduler)
 
@@ -3861,6 +3862,14 @@ glibc_fedora_ppc64le_builder = util.BuilderConfig(
         factory=glibc_build_factory)
 c['builders'].append(glibc_fedora_ppc64le_builder)
 
+glibc_ubuntu_riscv_builder = util.BuilderConfig(
+        name="glibc-ubuntu-riscv",
+        collapseRequests=True,
+        workernames=["starfive-riscv"], # note only uses one specific starfive
+        tags=["glibc", "ubuntu", "riscv"],
+        factory=glibc_factory)
+c['builders'].append(glibc_ubuntu_riscv_builder)
+
 glibc_gentoo_sparc_builder = util.BuilderConfig(
         name="glibc-gentoo-sparc",
         collapseRequests=True,
-- 
2.39.3


                 reply	other threads:[~2024-02-22 23:54 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=20240222235408.2220719-1-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).