From: Mark Wielaard <mark@klomp.org>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: gcc-rust@gcc.gnu.org, buildbot@sourceware.org
Subject: Re: ☠ Buildbot (GNU Toolchain): gccrust - failed 'make clean' (failure) (master)
Date: Fri, 22 Jul 2022 16:48:18 +0200 [thread overview]
Message-ID: <20220722144818.GA27274@gnu.wildebeest.org> (raw)
In-Reply-To: <YtnYEmU/RZm/EZ/U@wildebeest.org>
[-- Attachment #1: Type: text/plain, Size: 1355 bytes --]
Hi,
On Fri, Jul 22, 2022 at 12:49:54AM +0200, Mark Wielaard wrote:
> On Thu, Jul 21, 2022 at 10:38:18PM +0000, builder--- via Gcc-rust wrote:
> > A new failure has been detected on builder gccrust-bootstrap-debian-amd64 while building gccrust.
> >
> > Full details are available at:
> > https://builder.sourceware.org/buildbot/#builders/107/builds/43
> >
> > Build state: failed 'make clean' (failure)
> > Revision: 51f03d9d697b0f3fed65f85e88ce41d424c844fb
> > Worker: bb2
> > Build Reason: (unknown)
> > Blamelist: Thomas Schwinge <thomas@codesourcery.com>
> >
> > Steps:
> > [...]
> > - 16: make clean ( failure )
> > Logs:
> > - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/16/logs/stdio
>
> Sorry, this was supposed to simply be to save some space at the end
> of the build:
> https://sourceware.org/pipermail/buildbot/2022q3/000162.html
>
> Apparently make clean doesn't work as expected. I will try to look
> into it, but it might take one or two days till I have
> time. Apologies for the mess.
It only happens after a boostrap build. But I couldn't really figure
out what is going wrong. It looks like some parts of make clean
require bash while the debian-stable tester uses dash as default. For
now I just remove the whole build tree at the end instead of running
make clean.
Cheers,
Mark
[-- Attachment #2: 0001-Don-t-make-clean-after-a-gccrs-bootstrap.patch --]
[-- Type: text/plain, Size: 1216 bytes --]
From f2db122660f2f03632253493dd7ae801e9567056 Mon Sep 17 00:00:00 2001
From: Mark Wielaard <mark@klomp.org>
Date: Fri, 22 Jul 2022 16:39:58 +0200
Subject: [PATCH] Don't make clean after a gccrs bootstrap
It looks like after a bootstrap make clean gets confused.
Just blow away the whole builddir when we are done with it.
---
builder/master.cfg | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/builder/master.cfg b/builder/master.cfg
index 2047eaa..0d94e67 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -1686,7 +1686,10 @@ gccrust_bootstrap_factory.addStep(gccrust_make_bootstrap_step)
gccrust_bootstrap_factory.addStep(gccrust_check_bootstrap_step)
gccrust_bootstrap_factory.addStep(gccrust_check_check_step)
gccrust_bootstrap_factory.addSteps(gccrust_bunsen_steps)
-gccrust_bootstrap_factory.addStep(gccrust_make_clean_step)
+# It looks like after a bootstrap make clean gets confused
+# Just blow away the whole builddir when we are done with it
+#gccrust_bootstrap_factory.addStep(gccrust_make_clean_step)
+gccrust_bootstrap_factory.addStep(gccrust_rm_build_step)
gccrust_fedora_x86_64_builder = util.BuilderConfig(
name="gccrust-fedora-x86_64",
--
2.31.1
parent reply other threads:[~2022-07-22 14:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <YtnYEmU/RZm/EZ/U@wildebeest.org>]
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=20220722144818.GA27274@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
--cc=gcc-rust@gcc.gnu.org \
--cc=thomas@codesourcery.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).