From: Mark Wielaard <mark@klomp.org>
To: buildbot@sourceware.org
Cc: Mark Wielaard <mark@klomp.org>
Subject: [COMMITTED] Fix gccrust_bootstrap_factory steps
Date: Fri, 24 Jun 2022 10:50:57 +0200 [thread overview]
Message-ID: <20220624085057.13518-1-mark@klomp.org> (raw)
The steps were added to the gccrust_factory instead of the
gccrust_bootstrap_factory. Turning every builder into a full bootstrap
build. And leaving the bootstrap build empty.
---
builder/master.cfg | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/builder/master.cfg b/builder/master.cfg
index 2d1379f..a70a93b 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -1367,13 +1367,13 @@ gccrust_factory.addStep(gccrust_check_check_step)
gccrust_factory.addSteps(gccrust_bunsen_steps)
gccrust_bootstrap_factory = util.BuildFactory()
-gccrust_factory.addStep(gccrust_git_step)
-gccrust_factory.addStep(gccrust_rm_build_step)
-gccrust_factory.addStep(gccrust_configure_bootstrap_step)
-gccrust_factory.addStep(gccrust_make_step)
-gccrust_factory.addStep(gccrust_check_step)
-gccrust_factory.addStep(gccrust_check_check_step)
-gccrust_factory.addSteps(gccrust_bunsen_steps)
+gccrust_bootstrap_factory.addStep(gccrust_git_step)
+gccrust_bootstrap_factory.addStep(gccrust_rm_build_step)
+gccrust_bootstrap_factory.addStep(gccrust_configure_bootstrap_step)
+gccrust_bootstrap_factory.addStep(gccrust_make_step)
+gccrust_bootstrap_factory.addStep(gccrust_check_step)
+gccrust_bootstrap_factory.addStep(gccrust_check_check_step)
+gccrust_bootstrap_factory.addSteps(gccrust_bunsen_steps)
gccrust_fedora_x86_64_builder = util.BuilderConfig(
name="gccrust-fedora-x86_64",
--
2.30.2
reply other threads:[~2022-06-24 8:51 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=20220624085057.13518-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).