public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: buildbot@builder.wildebeest.org
To: gcc-rust@gcc.gnu.org
Subject: ☠ Buildbot (Wildebeest Builder): gccrust - failed compile (failure) (master)
Date: Mon, 11 Apr 2022 16:59:05 +0000	[thread overview]
Message-ID: <20220411165905.E06BF81A9C8@builder.wildebeest.org> (raw)

A new failure has been detected on builder gccrust-debian-arm64 while building gccrust.

Full details are available at:
    https://builder.wildebeest.org/buildbot/#builders/58/builds/1807

Build state: failed compile (failure)
Revision: 46e0068fc0128207ac69bde5cb53d7eeb6943cbb
Worker: debian-arm64
Build Reason: (unknown)
Blamelist: Arthur Cohen <arthur.cohen@embecosm.com>, bors[bot] <26634292+bors[bot]@users.noreply.github.com>

Steps:

- 0: worker_preparation ( success )

- 1: git checkout ( success )
    Logs:
        - stdio: https://builder.wildebeest.org/buildbot/#builders/58/builds/1807/steps/1/logs/stdio

- 2: rm -rf gccrs-build ( success )
    Logs:
        - stdio: https://builder.wildebeest.org/buildbot/#builders/58/builds/1807/steps/2/logs/stdio

- 3: configure ( success )
    Logs:
        - stdio: https://builder.wildebeest.org/buildbot/#builders/58/builds/1807/steps/3/logs/stdio

- 4: make ( failure )
    Logs:
        - stdio: https://builder.wildebeest.org/buildbot/#builders/58/builds/1807/steps/4/logs/stdio
        - warnings (58): https://builder.wildebeest.org/buildbot/#builders/58/builds/1807/steps/4/logs/warnings__58_


             reply	other threads:[~2022-04-11 16:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 16:59 buildbot [this message]
2022-04-12 13:07 buildbot
2022-04-12 13:55 ` Mark Wielaard
2022-04-12 16:08 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=20220411165905.E06BF81A9C8@builder.wildebeest.org \
    --to=buildbot@builder.wildebeest.org \
    --cc=gcc-rust@gcc.gnu.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).