From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
To: Mark Wielaard <mark@klomp.org>
Cc: elfutils-devel@sourceware.org, Yonggang Luo <luoyonggang@gmail.com>
Subject: Re: ☠ Buildbot (GNU Toolchain): elfutils - failed configure (failure) (master)
Date: Mon, 12 Dec 2022 11:33:03 -0500 [thread overview]
Message-ID: <m3cz8o8tvk.fsf@fitzsim.org> (raw)
In-Reply-To: <Y5c16WML5SI9JPnc@wildebeest.org> (Mark Wielaard's message of "Mon, 12 Dec 2022 15:08:41 +0100")
Hi Mark,
Mark Wielaard <mark@klomp.org> writes:
> On Mon, Dec 12, 2022 at 02:01:49PM +0000, builder--- via Elfutils-devel wrote:
>> A new failure has been detected on builder elfutils-debian-ppc64 while building elfutils.
>>
>> Full details are available at:
>> https://builder.sourceware.org/buildbot/#builders/63/builds/113
>>
>> Build state: failed configure (failure)
>> Revision: dab89fba0e84c948fb270e541d1d1313afd2c2c3
>> Worker: debian-ppc64
>> Build Reason: (unknown)
>> Blamelist: Yonggang Luo <luoyonggang@gmail.com>
>> [...]
>> - 4: configure ( failure )
>> Logs:
>> - stdio: https://builder.sourceware.org/buildbot/#builders/63/builds/113/steps/4/logs/stdio
>
> That looks like a disk space issue:
>
> ./config.status: line 1372: printf: write error: No space left on device
> config.status: error: in `/var/lib/buildbot/workers/wildebeest/elfutils-debian-ppc64/build':
> ./config.status: line 127: printf: write error: No space left on device
Thanks for forwarding.
> Tom, could you take a look?
I didn't see anything particularly deletion-worthy, so I'm going to take
the node down and try to enlarge its root file system.
Thomas
prev parent reply other threads:[~2022-12-12 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 14:01 builder
2022-12-12 14:08 ` Mark Wielaard
2022-12-12 16:33 ` Thomas Fitzsimmons [this message]
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=m3cz8o8tvk.fsf@fitzsim.org \
--to=fitzsim@fitzsim.org \
--cc=elfutils-devel@sourceware.org \
--cc=luoyonggang@gmail.com \
--cc=mark@klomp.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).