From: Mark Wielaard <mark@klomp.org>
To: builder@sourceware.org, Arthur Cohen <arthur.cohen@embecosm.com>
Cc: gcc-rust@gcc.gnu.org
Subject: Re: ☠ Buildbot (GNU Toolchain): gccrust - failed compile (failure) (master)
Date: Fri, 22 Apr 2022 15:36:33 +0200 [thread overview]
Message-ID: <3b8dd0bbbad76cfe0191f3e7ece338ca8825f22b.camel@klomp.org> (raw)
In-Reply-To: <20220422132925.A8FC43858403@sourceware.org>
Hi,
On Fri, 2022-04-22 at 13:29 +0000, builder--- via Gcc-rust wrote:
> 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/20
>
> Build state: failed compile (failure)
> Revision: bfe8ffef8668a0fc7be973f3b9de6e148019f94e
> Worker: debian-arm64
> Build Reason: (unknown)
> Blamelist: Arthur Cohen <arthur.cohen@embecosm.com>, bors[bot]
> <26634292+bors[bot]@users.noreply.github.com>
>
> Steps:
> [...]
>
https://builder.sourceware.org/buildbot/#builders/34/builds/20/steps/3/logs/stdio
>
> - 4: make ( failure )
> Logs:
> - stdio:
> https://builder.sourceware.org/buildbot/#builders/34/builds/20/steps/4/logs/stdio
Sorry, that was again the buildbot worker. It ran out of memory again
and the oom killer killed g++. Drat. I'll add more swap.
Cheers,
Mark
next prev parent reply other threads:[~2022-04-22 13:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 13:29 builder
2022-04-22 13:36 ` Mark Wielaard [this message]
-- 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-28 11:17 builder
2022-04-28 11:40 ` Mark Wielaard
2022-04-25 20:37 builder
2022-04-22 14:15 builder
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=3b8dd0bbbad76cfe0191f3e7ece338ca8825f22b.camel@klomp.org \
--to=mark@klomp.org \
--cc=arthur.cohen@embecosm.com \
--cc=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).