public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: dwz@sourceware.org
Subject: Re: Buildbot failure in Wildebeest Builder on whole buildset
Date: Tue, 01 Jan 2019 00:00:00 -0000	[thread overview]
Message-ID: <9594b14416b02d41c69f1ce0633b3c9be3733399.camel@klomp.org> (raw)
In-Reply-To: <20191021101008.A4F7D81A9FF@builder.wildebeest.org>

On Mon, 2019-10-21 at 10:10 +0000, buildbot@builder.wildebeest.org
wrote:
> The Buildbot has detected a failed build on builder whole buildset
> while building dwz.
> Full details are available at:
>     https://builder.wildebeest.org/buildbot/#builders/25/builds/108
> 
> Buildbot URL: https://builder.wildebeest.org/buildbot/
> 
> Worker for this Build: fedora-s390x
> 
> Build Reason: <unknown>
> Blamelist: Tom de Vries <tdevries@suse.de>
> 
> BUILD FAILED: failed compile (failure)

Sorry, the s390x buildbot ran out of disk space again.
It has been cleaned up and the build now succeeds:
https://builder.wildebeest.org/buildbot/#/builders/25/builds/109

But there is a suspicious snprintf warning.

Cheers,

Mark

  reply	other threads:[~2019-10-21 10:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-01  0:00 buildbot
2019-01-01  0:00 ` Mark Wielaard [this message]
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 ` Mark Wielaard
2019-01-01  0:00   ` Tom de Vries
2020-01-01  0:00 buildbot
2020-01-01  0:00 ` Mark Wielaard
2020-07-19 23:00 buildbot
2020-07-19 23:17 ` Mark Wielaard
2020-10-13 21:29 buildbot
2020-10-13 22:20 ` Mark Wielaard
2020-10-14 10:36   ` Mark Wielaard
2021-03-25  8:41 buildbot
2021-03-26 13:04 buildbot

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=9594b14416b02d41c69f1ce0633b3c9be3733399.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=dwz@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).