public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: builder@sourceware.org
To: libabigail@sourceware.org
Subject: ☠ Buildbot (GNU Toolchain): libabigail - failed update (failure) (master)
Date: Fri, 01 Jul 2022 13:14:04 +0000	[thread overview]
Message-ID: <20220701131404.E11253857BB4@sourceware.org> (raw)

A new failure has been detected on builder libabigail-fedora-ppc64le while building libabigail.

Full details are available at:
    https://builder.sourceware.org/buildbot/#builders/38/builds/45

Build state: failed update (failure)
Revision: (unknown)
Worker: fedora-ppc64le
Build Reason: (unknown)
Blamelist: Giuliano Procida <gprocida@google.com>

Steps:

- 0: worker_preparation ( success )

- 1: git checkout ( failure )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/38/builds/45/steps/1/logs/stdio


                 reply	other threads:[~2022-07-01 13:14 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=20220701131404.E11253857BB4@sourceware.org \
    --to=builder@sourceware.org \
    --cc=libabigail@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).