public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Luis Machado <luis.machado@arm.com>, gdb-testers@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: Re: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed test (failure) (master)
Date: Mon, 16 May 2022 10:44:37 +0200 [thread overview]
Message-ID: <8b8f6cc8928d1f978bba3a09f4374209e93a4e84.camel@klomp.org> (raw)
In-Reply-To: <416d9d21-188f-f9a6-3e8b-02823d711ab6@arm.com>
Hi Luis,
On Mon, 2022-05-16 at 09:25 +0100, Luis Machado wrote:
> What kind of hardware is this debian-armhf node?
It is this worker:
https://builder.sourceware.org/buildbot/#/workers/7
Debian GNU/Linux 10 (buster)
Linux 5.15.25-rockchip #22.02.1 SMP PREEMPT Sun Feb 27 09:23:03 UTC 2022
GNU C Library (Debian GLIBC 2.28-10+deb10u1) stable release version 2.28.
g++ 8.3.0
GNU objdump (GNU Binutils for Debian) 2.31.1
Which is a small Rockchip RK3288 Asus Tinker Board S
It only has 2GB of memory (and 1 GB swap).
Even though it is small and not that fast you can see it is doing
builds for elfutils, binutils, valgrind, libabigail and gdb.
Cheers,
Mark
next prev parent reply other threads:[~2022-05-16 8:44 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 20:18 builder
2022-05-15 15:04 ` Mark Wielaard
2022-05-16 8:25 ` Luis Machado
2022-05-16 8:44 ` Mark Wielaard [this message]
2022-05-16 9:12 ` Luis Machado
2022-05-15 0:25 builder
2022-05-17 5:52 builder
2022-05-17 10:50 builder
2022-05-18 0:23 builder
2022-05-18 13:02 builder
2022-05-18 13:45 ` Mark Wielaard
2022-05-18 16:30 ` Luis Machado
2022-05-31 15:39 builder
2022-06-07 18:34 builder
2022-07-08 14:07 builder
2022-07-15 0:19 builder
2022-07-15 17:52 builder
2022-07-19 14:54 builder
2022-07-29 7:49 builder
2022-07-30 0:27 builder
2022-08-03 20:03 builder
2022-08-31 17:30 builder
2022-08-31 18:22 builder
2022-09-12 8:31 builder
2022-09-13 12:20 builder
2022-10-16 17:05 builder
2022-10-16 17:15 builder
2022-10-16 17:19 builder
2022-10-16 17:23 builder
2022-10-16 17:23 builder
2022-10-16 17:51 builder
2022-10-16 18:51 builder
2022-10-16 19:01 builder
2022-10-18 15:33 builder
2022-10-26 7:45 builder
2022-10-26 12:16 builder
2022-11-07 16:53 builder
2022-11-11 15:20 builder
2022-11-22 0:29 builder
2022-11-28 16:18 builder
2022-11-28 16:22 builder
2022-12-06 15:13 builder
2022-12-15 0:31 builder
2022-12-22 4:09 builder
2023-01-11 1:01 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=8b8f6cc8928d1f978bba3a09f4374209e93a4e84.camel@klomp.org \
--to=mark@klomp.org \
--cc=gdb-testers@sourceware.org \
--cc=luis.machado@arm.com \
--cc=tromey@adacore.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).