From: builder@sourceware.org
To: gcc-rust@gcc.gnu.org
Subject: ☠ Buildbot (Sourceware): gccrust - failed compile (failure) (master)
Date: Tue, 26 Mar 2024 18:44:24 +0000 [thread overview]
Message-ID: <20240326184424.93D953858C56@sourceware.org> (raw)
A new failure has been detected on builder gccrust-fedora-ppc64le while building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/19/builds/1856
Build state: failed compile (failure)
Revision: b281eb02d4caeadf087c37c3312039aa45c75da9
Worker: fedora-ppc64le
Build Reason: (unknown)
Blamelist: Arthur Cohen <arthur.cohen@embecosm.com>, Thomas Schwinge <tschwinge@baylibre.com>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/19/builds/1856/steps/1/logs/stdio
- 2: rm -rf gccrs-build ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/19/builds/1856/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/19/builds/1856/steps/3/logs/stdio
- config.log: https://builder.sourceware.org/buildbot/#/builders/19/builds/1856/steps/3/logs/config_log
- 4: make ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/19/builds/1856/steps/4/logs/stdio
- warnings (8): https://builder.sourceware.org/buildbot/#/builders/19/builds/1856/steps/4/logs/warnings__8_
next reply other threads:[~2024-03-26 18:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 18:44 builder [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-16 9:03 builder
2024-04-16 8:59 builder
2024-03-25 12:49 builder
2024-03-25 12:47 builder
2024-03-25 10:00 builder
2024-03-12 17:12 builder
2024-03-12 13:02 builder
2024-02-29 18:25 builder
2024-02-29 20:01 ` Thomas Schwinge
2024-02-29 18:09 builder
2024-02-29 20:00 ` Thomas Schwinge
2024-02-29 20:22 ` Mark Wielaard
2024-02-29 22:08 ` Jakub Dupak
2024-03-01 10:22 ` Arthur Cohen
2024-03-01 10:24 ` Arthur Cohen
2024-03-02 19:57 ` Mark Wielaard
2024-02-26 19:35 builder
2023-09-14 22:57 builder
2023-08-28 16:01 builder
2023-08-01 16:40 builder
2023-07-30 18:43 builder
2023-07-30 18:40 builder
2023-07-29 17:23 builder
2023-06-25 21:47 builder
2023-06-20 9:42 builder
2023-04-27 23:54 builder
2023-04-27 23:42 builder
2023-04-13 12:53 builder
2023-03-17 18:01 builder
2023-02-13 12:36 builder
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=20240326184424.93D953858C56@sourceware.org \
--to=builder@sourceware.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).