public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: buildbot@sourceware.org
Cc: Sam James <sam@gentoo.org>, Mark Wielaard <mark@klomp.org>
Subject: [PATCH] Turn gccrust-bootstrap-gentoo-sparc into gccrust-gentoo-sparc builder
Date: Wed,  1 Feb 2023 15:02:57 +0100	[thread overview]
Message-ID: <20230201140257.257769-1-mark@klomp.org> (raw)

The full bootstrap build times out even with 64 cores since there
is some compile that takes +20 minutes using just 1 core. So change
the build to a simple build only gccrs builder till we figure out
why a gcc bootstrap is so slow on this setup.
---
 builder/master.cfg | 17 ++++++++---------
 1 file changed, 8 insertions(+), 9 deletions(-)

diff --git a/builder/master.cfg b/builder/master.cfg
index 9600120..46e7cf9 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -677,6 +677,7 @@ gccrust_scheduler = schedulers.SingleBranchScheduler(
                       "gccrust-debian-testing-x86_64",
                       "gccrust-debian-i386",
                       "gccrust-fedora-arm64",
+                      "gccrust-gentoo-sparc",
                       "gccrust-fedora-ppc64le",
                       "gccrust-fedora-s390x",
                       "gccrust-debian-ppc64",
@@ -692,8 +693,7 @@ gccrust_bootstrap_scheduler = schedulers.SingleBranchScheduler(
         onlyImportant=True,
         treeStableTimer=10*60,
         reason="gccrust project master branch gccrs files update",
-        builderNames=["gccrust-bootstrap-debian-amd64",
-                      "gccrust-bootstrap-gentoo-sparc"])
+        builderNames=["gccrust-bootstrap-debian-amd64"])
 c['schedulers'].append(gccrust_bootstrap_scheduler)
 
 # Only trigger scheduler for changes to binutils (or deps)
@@ -2170,13 +2170,12 @@ gccrust_bootstrap_debian_amd64_builder = util.BuilderConfig(
         factory=gccrust_bootstrap_factory)
 c['builders'].append(gccrust_bootstrap_debian_amd64_builder)
 
-gccrust_bootstrap_gentoo_sparc_builder = util.BuilderConfig(
-        name="gccrust-bootstrap-gentoo-sparc",
-	workernames=["gentoo-sparc-big"],
-        tags=["gccrust-bootstrap", "gentoo", "sparc"],
-        collapseRequests=True,
-        factory=gccrust_bootstrap_factory)
-c['builders'].append(gccrust_bootstrap_gentoo_sparc_builder)
+gccrust_gentoo_sparc_builder = util.BuilderConfig(
+        name="gccrust-gentoo-sparc",
+	workernames=sparc_workers,
+        tags=["gccrust", "gentoo", "sparc"],
+        factory=gccrust_factory)
+c['builders'].append(gccrust_gentoo_sparc_builder)
 
 # binutils build steps, factory and builders
 
-- 
2.39.1


                 reply	other threads:[~2023-02-01 14:03 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=20230201140257.257769-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).