public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Andrew Burgess <aburgess@redhat.com>, gdb-testers@sourceware.org
Subject: Re: ☠ Buildbot (Sourceware): binutils-gdb - failed test (failure) test (failure) (master)
Date: Fri, 14 Jun 2024 15:26:30 +0200	[thread overview]
Message-ID: <be797a212a6e9dd0aa2998cdbdc2671729d3bc65.camel@klomp.org> (raw)
In-Reply-To: <20240614114809.203C83882100@sourceware.org>

Hi Andrew,

On Fri, 2024-06-14 at 11:48 +0000, builder--- via Gdb-testers wrote:
> A new failure has been detected on builder gdb-debian-i386 while building binutils-gdb.
> 
> Full details are available at:
>     https://builder.sourceware.org/buildbot/#/builders/105/builds/6932
> 
> Build state: failed test (failure) test (failure)
> Revision: bf616be99153b43c1077be9dbb7b081b4c080031
> Worker: debian-i386
> Build Reason: (unknown)
> Blamelist: Andrew Burgess <aburgess@redhat.com>

It looks like you latest patch caused breakage on i386 with
RUNTESTFLAGS=--target_board=native-gdbserver and --target_board=native-
extended-gdbserver but a "native" make check-gdb is fine as are all
other arches.

Cheers,

Mark

  reply	other threads:[~2024-06-14 13:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-14 11:48 builder
2024-06-14 13:26 ` Mark Wielaard [this message]
2024-06-14 21:04   ` Andrew Burgess
2024-06-18 17:16     ` Mark Wielaard
2024-06-19  9:38       ` Andrew Burgess
  -- strict thread matches above, loose matches on Subject: below --
2024-03-25 20:26 builder
2023-10-22  0:34 builder
2023-10-19 19:19 builder
2023-10-05 12:37 builder
2023-10-04 19:58 builder
2023-09-19 12:47 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=be797a212a6e9dd0aa2998cdbdc2671729d3bc65.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=aburgess@redhat.com \
    --cc=gdb-testers@sourceware.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).