public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: builder@sourceware.org
Cc: Philip Herron <philip.herron@embecosm.com>, gcc-rust@gcc.gnu.org
Subject: Re: ☠ Buildbot (GNU Toolchain): gccrust - failed compile (failure) (master)
Date: Thu, 21 Apr 2022 21:45:14 +0200	[thread overview]
Message-ID: <YmG0Sv68sSi1DXbU@wildebeest.org> (raw)
In-Reply-To: <20220421183237.2B28C38346BE@sourceware.org>

Hi,

On Thu, Apr 21, 2022 at 06:32:37PM +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/8
> 
> Build state: failed compile (failure)
> Revision: 03ec66cf1162f139ba873e5d8237a1dfad989937
> Worker: debian-arm64
> Build Reason: (unknown)
> Blamelist: Philip Herron <philip.herron@embecosm.com>, bors[bot] <26634292+bors[bot]@users.noreply.github.com>
>
> Steps:
> [...]
> - 4: make ( failure )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/34/builds/8/steps/4/logs/stdio

Sorry, that was me. When migrating to sourceware I overrated the
little boards specs. It actually have 6 cores (2 slow, 4 fast), so I
said you could use 4 cpus at the same time. But the board has only 4GB
of memory. A make -j4 might cause a swap storm. So I reduced the
number of usable cores to 3:

https://sourceware.org/git/?p=builder.git;a=commit;h=3c098c8e16355f528b121c61898542a4b90cd003

Cheers,

Mark

  reply	other threads:[~2022-04-21 19:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21 18:32 builder
2022-04-21 19:45 ` Mark Wielaard [this message]
2022-04-21 20:19 builder
2022-04-22 13:29 builder
2022-04-22 13:36 ` Mark Wielaard
2022-04-22 14:15 builder
2022-04-25 20:37 builder
2022-04-28 11:17 builder
2022-04-28 11:40 ` Mark Wielaard
2022-06-24  9:15 builder
2022-06-24  9:21 builder
2022-06-24  9:31 ` Mark Wielaard
2022-06-27  9:16 builder
2022-08-25 15:31 builder
2022-08-25 16:36 builder
2022-08-25 16:36 builder
     [not found] <20220825153123.2C3763852759@sourceware.org>
2022-08-25 16:40 ` Mark Wielaard
2022-10-21 15:14 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=YmG0Sv68sSi1DXbU@wildebeest.org \
    --to=mark@klomp.org \
    --cc=builder@sourceware.org \
    --cc=gcc-rust@gcc.gnu.org \
    --cc=philip.herron@embecosm.com \
    /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).