From: Mark Wielaard <mark@klomp.org>
To: libabigail@sourceware.org
Cc: Ben Woodard <woodard@redhat.com>,
"Dmitry V. Levin" <ldv@strace.io>,
Dodji Seketeli <dodji@redhat.com>,
"Guillermo E. Martinez" <guillermo.e.martinez@oracle.com>
Subject: Re: ☠ Buildbot (Sourceware): libabigail - failed test (failure) (master)
Date: Fri, 19 May 2023 00:31:36 +0200 [thread overview]
Message-ID: <20230518223136.GD13835@gnu.wildebeest.org> (raw)
In-Reply-To: <20230518213228.971653858D39@sourceware.org>
Hi all,
On Thu, May 18, 2023 at 09:32:28PM +0000, builder@sourceware.org wrote:
> A new failure has been detected on builder libabigail-gentoo-sparc while building libabigail.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/234/builds/76
>
> Build state: failed test (failure)
> Revision: 06e8d54d0404ccf2a103804ec568797822152b69
> Worker: gentoo-sparc
> Build Reason: (unknown)
> Blamelist: Ben Woodard <woodard@redhat.com>, Dmitry V. Levin <ldv@strace.io>, Dodji Seketeli <dodji@redhat.com>, Guillermo E. Martinez <guillermo.e.martinez@oracle.com>, Mark Wielaard <mark@klomp.org>
This obviously wasn't a new failure. sparc has been failing from the
start. There was a hickup with the sparc machine yesterday and somehow
the buildbot thought it should remind everybody about this failure.
I haven't looked into it myself. But it is definitely sparc specific,
all other arches are green:
https://builder.sourceware.org/buildbot/#/builders?tags=libabigail
Cheers,
Mark
next parent reply other threads:[~2023-05-18 22:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230518213228.971653858D39@sourceware.org>
2023-05-18 22:31 ` Mark Wielaard [this message]
2024-05-06 17:59 builder
-- strict thread matches above, loose matches on Subject: below --
2024-05-06 17:27 builder
2024-03-02 1:40 builder
2023-10-02 21:47 builder
2023-09-07 15:48 builder
2023-09-07 15:45 builder
2023-09-07 15:13 builder
2023-05-18 21:32 builder
2023-04-14 14:17 builder
2023-04-03 15:24 builder
2023-03-22 17:23 builder
2023-03-02 22:08 builder
2023-03-02 21:57 builder
2023-03-02 21:57 builder
2023-03-02 21:37 builder
2023-03-02 21:37 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=20230518223136.GD13835@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=dodji@redhat.com \
--cc=guillermo.e.martinez@oracle.com \
--cc=ldv@strace.io \
--cc=libabigail@sourceware.org \
--cc=woodard@redhat.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).