public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: builder@sourceware.org
To: "Arthur Cohen" <arthur.cohen@embecosm.com>
Cc: gcc-rust@gcc.gnu.org
Subject: ☠ Buildbot (GNU Toolchain): gccrust - failed compile (failure) (master)
Date: Thu, 28 Apr 2022 11:17:45 +0000	[thread overview]
Message-ID: <20220428111745.CDE3C3858407@sourceware.org> (raw)

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

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

Build state: failed compile (failure)
Revision: 34c73a75cf0043d3b9bb222c1c506aae18f27195
Worker: debian-arm64
Build Reason: (unknown)
Blamelist: Arthur Cohen <arthur.cohen@embecosm.com>

Steps:

- 0: worker_preparation ( success )

- 1: git checkout ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/34/builds/50/steps/1/logs/stdio

- 2: rm -rf gccrs-build ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/34/builds/50/steps/2/logs/stdio

- 3: configure ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/34/builds/50/steps/3/logs/stdio

- 4: make ( failure )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/34/builds/50/steps/4/logs/stdio
        - warnings (56): https://builder.sourceware.org/buildbot/#builders/34/builds/50/steps/4/logs/warnings__56_


             reply	other threads:[~2022-04-28 11:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 11:17 builder [this message]
2022-04-28 11:40 ` Mark Wielaard
  -- strict thread matches above, loose matches on Subject: below --
2022-10-21 15:14 builder
     [not found] <20220825153123.2C3763852759@sourceware.org>
2022-08-25 16:40 ` Mark Wielaard
2022-08-25 16:36 builder
2022-08-25 16:36 builder
2022-08-25 15:31 builder
2022-06-27  9:16 builder
2022-06-24  9:21 builder
2022-06-24  9:31 ` Mark Wielaard
2022-06-24  9:15 builder
2022-04-25 20:37 builder
2022-04-22 14:15 builder
2022-04-22 13:29 builder
2022-04-22 13:36 ` Mark Wielaard
2022-04-21 20:19 builder
2022-04-21 18:32 builder
2022-04-21 19:45 ` Mark Wielaard

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=20220428111745.CDE3C3858407@sourceware.org \
    --to=builder@sourceware.org \
    --cc=arthur.cohen@embecosm.com \
    --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).