From: Thomas Schwinge <tschwinge@baylibre.com>
To: Arthur Cohen <arthur.cohen@embecosm.com>, Mark Wielaard <mark@klomp.org>
Cc: builder@sourceware.org, gcc-rust@gcc.gnu.org
Subject: Re: ☠ Buildbot (Sourceware): gccrust - failed compile (failure) (master)
Date: Thu, 29 Feb 2024 21:00:13 +0100 [thread overview]
Message-ID: <87msrjghwy.fsf@euler.schwinge.ddns.net> (raw)
In-Reply-To: <20240229180922.810A93858C52@sourceware.org>
Hi!
Three 'cargo' ('command not found') as well as
one 'rustc' ('error[E0658]: `let...else` statements are unstable')
errors:
On 2024-02-29T18:09:22+0000, builder@sourceware.org wrote:
> A new failure has been detected on builder gccrust-fedora-x86_64 while building gccrust.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#/builders/16/builds/1917
>
> Build state: failed compile (failure)
> Revision: e9de5b410da43cb2ac5f9865756153648e6f078b
> Worker: bb3
> 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/16/builds/1917/steps/1/logs/stdio
>
> - 2: rm -rf gccrs-build ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#/builders/16/builds/1917/steps/2/logs/stdio
>
> - 3: configure ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#/builders/16/builds/1917/steps/3/logs/stdio
> - config.log: https://builder.sourceware.org/buildbot/#/builders/16/builds/1917/steps/3/logs/config_log
>
> - 4: make ( failure )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#/builders/16/builds/1917/steps/4/logs/stdio
> - warnings (10): https://builder.sourceware.org/buildbot/#/builders/16/builds/1917/steps/4/logs/warnings__10_
/bin/sh: line 1: cargo: command not found
make[2]: *** [../../gccrs/gcc/rust/Make-lang.in:412: rust/libformat_parser.a] Error 127
> A new failure has been detected on builder gccrust-debian-i386 while building gccrust.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#/builders/27/builds/1934
>
> Build state: failed compile (failure)
> Revision: e9de5b410da43cb2ac5f9865756153648e6f078b
> Worker: debian-i386
> 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/27/builds/1934/steps/1/logs/stdio
>
> - 2: rm -rf gccrs-build ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#/builders/27/builds/1934/steps/2/logs/stdio
>
> - 3: configure ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#/builders/27/builds/1934/steps/3/logs/stdio
> - config.log: https://builder.sourceware.org/buildbot/#/builders/27/builds/1934/steps/3/logs/config_log
>
> - 4: make ( failure )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#/builders/27/builds/1934/steps/4/logs/stdio
> - warnings (5): https://builder.sourceware.org/buildbot/#/builders/27/builds/1934/steps/4/logs/warnings__5_
cargo build --manifest-path ../../gccrs/gcc/../libgrust/libformat_parser/Cargo.toml --release # FIXME: Not always release, right?
[...]
Compiling libc v0.2.152
Compiling unicode-xid v0.2.4
Compiling generic_format_parser v0.1.0 (/srv/buildbot/worker/gccrust-debian-i386/gccrs/libgrust/libformat_parser/generic_format_parser)
error[E0658]: `let...else` statements are unstable
--> generic_format_parser/src/lib.rs:994:5
|
994 | / let Some(unescaped) = unescape_string(snippet) else {
995 | | return InputStringKind::NotALiteral;
996 | | };
| |______^
|
= note: see issue #87335 <https://github.com/rust-lang/rust/issues/87335> for more information
For more information about this error, try `rustc --explain E0658`.
error: could not compile `generic_format_parser` due to previous error
warning: build failed, waiting for other jobs to finish...
make[2]: *** [../../gccrs/gcc/rust/Make-lang.in:412: rust/libformat_parser.a] Error 101
> A new failure has been detected on builder gccrust-debian-testing-x86_64 while building gccrust.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#/builders/146/builds/1682
>
> Build state: failed compile (failure)
> Revision: e9de5b410da43cb2ac5f9865756153648e6f078b
> Worker: bb1-1
> 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/146/builds/1682/steps/1/logs/stdio
>
> - 2: rm -rf gccrs-build ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#/builders/146/builds/1682/steps/2/logs/stdio
>
> - 3: configure ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#/builders/146/builds/1682/steps/3/logs/stdio
> - config.log: https://builder.sourceware.org/buildbot/#/builders/146/builds/1682/steps/3/logs/config_log
>
> - 4: make ( failure )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#/builders/146/builds/1682/steps/4/logs/stdio
> - warnings (2): https://builder.sourceware.org/buildbot/#/builders/146/builds/1682/steps/4/logs/warnings__2_
/bin/bash: line 1: cargo: command not found
make[2]: *** [../../gccrs/gcc/rust/Make-lang.in:412: rust/libformat_parser.a] Error 127
> A new failure has been detected on builder gccrust-fedora-arm64 while building gccrust.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#/builders/179/builds/1675
>
> Build state: failed compile (failure)
> Revision: e9de5b410da43cb2ac5f9865756153648e6f078b
> Worker: fedora-arm64
> 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/179/builds/1675/steps/1/logs/stdio
>
> - 2: rm -rf gccrs-build ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#/builders/179/builds/1675/steps/2/logs/stdio
>
> - 3: configure ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#/builders/179/builds/1675/steps/3/logs/stdio
> - config.log: https://builder.sourceware.org/buildbot/#/builders/179/builds/1675/steps/3/logs/config_log
>
> - 4: make ( failure )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#/builders/179/builds/1675/steps/4/logs/stdio
> - warnings (10): https://builder.sourceware.org/buildbot/#/builders/179/builds/1675/steps/4/logs/warnings__10_
/bin/sh: line 1: cargo: command not found
make[2]: *** [../../gccrs/gcc/rust/Make-lang.in:412: rust/libformat_parser.a] Error 127
Grüße
Thomas
next prev parent reply other threads:[~2024-02-29 20:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 18:09 builder
2024-02-29 20:00 ` Thomas Schwinge [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2024-04-16 9:03 builder
2024-04-16 8:59 builder
2024-03-26 18:44 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-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=87msrjghwy.fsf@euler.schwinge.ddns.net \
--to=tschwinge@baylibre.com \
--cc=arthur.cohen@embecosm.com \
--cc=builder@sourceware.org \
--cc=gcc-rust@gcc.gnu.org \
--cc=mark@klomp.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).