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: Wed, 01 Jan 2020 00:00:00 -0000	[thread overview]
Message-ID: <e18f18eabefbbf7b01513b47dd9a07b5962bf9e4.camel@klomp.org> (raw)
In-Reply-To: <20200116141838.34F6081A9E4@builder.wildebeest.org>

Hi,

On Thu, 2020-01-16 at 14:18 +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/20/builds/202

Just for the record. This was because of a sudden high load on
sourceware.org where the dwz.git repo is hosted. This caused the git
update on some builders to fail. The situation has been restored and
all builds are green again.

Cheers,

Mark

  reply	other threads:[~2020-01-17 10:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-01  0:00 buildbot
2020-01-01  0:00 ` Mark Wielaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-03-26 13:04 buildbot
2021-03-25  8:41 buildbot
2020-10-13 21:29 buildbot
2020-10-13 22:20 ` Mark Wielaard
2020-10-14 10:36   ` Mark Wielaard
2020-07-19 23:00 buildbot
2020-07-19 23:17 ` Mark Wielaard
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
2019-01-01  0:00 buildbot
2019-01-01  0:00 buildbot
2019-01-01  0:00 ` Mark Wielaard
2019-01-01  0:00 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=e18f18eabefbbf7b01513b47dd9a07b5962bf9e4.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).