public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: builder@sourceware.org
To: gdb-testers@sourceware.org
Subject: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed test (failure) (master)
Date: Sun, 15 May 2022 00:25:58 +0000	[thread overview]
Message-ID: <20220515002558.E92F13858D32@sourceware.org> (raw)

A new failure has been detected on builder gdb-debian-armhf while building binutils-gdb.

Full details are available at:
    https://builder.sourceware.org/buildbot/#builders/72/builds/183

Build state: failed test (failure)
Revision: 6d8b70895c19a3eb4cd44742c09af323031bc9a2
Worker: debian-armhf
Build Reason: (unknown)
Blamelist: GDB Administrator <gdbadmin@sourceware.org>

Steps:

- 0: worker_preparation ( success )

- 1: git checkout ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/72/builds/183/steps/1/logs/stdio

- 2: rm -rf gdb-build ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/72/builds/183/steps/2/logs/stdio

- 3: configure ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/72/builds/183/steps/3/logs/stdio

- 4: make ( warnings )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/72/builds/183/steps/4/logs/stdio
        - warnings (25): https://builder.sourceware.org/buildbot/#builders/72/builds/183/steps/4/logs/warnings__25_

- 5: make check-gdb ( failure )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/72/builds/183/steps/5/logs/stdio
        - gdb.sum: https://builder.sourceware.org/buildbot/#builders/72/builds/183/steps/5/logs/gdb_sum
        - gdb.log: https://builder.sourceware.org/buildbot/#builders/72/builds/183/steps/5/logs/gdb_log



             reply	other threads:[~2022-05-15  0:25 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-15  0:25 builder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-11  1:01 builder
2022-12-22  4:09 builder
2022-12-15  0:31 builder
2022-12-06 15:13 builder
2022-11-28 16:22 builder
2022-11-28 16:18 builder
2022-11-22  0:29 builder
2022-11-11 15:20 builder
2022-11-07 16:53 builder
2022-10-26 12:16 builder
2022-10-26  7:45 builder
2022-10-18 15:33 builder
2022-10-16 19:01 builder
2022-10-16 18:51 builder
2022-10-16 17:51 builder
2022-10-16 17:23 builder
2022-10-16 17:23 builder
2022-10-16 17:19 builder
2022-10-16 17:15 builder
2022-10-16 17:05 builder
2022-09-13 12:20 builder
2022-09-12  8:31 builder
2022-08-31 18:22 builder
2022-08-31 17:30 builder
2022-08-03 20:03 builder
2022-07-30  0:27 builder
2022-07-29  7:49 builder
2022-07-19 14:54 builder
2022-07-15 17:52 builder
2022-07-15  0:19 builder
2022-07-08 14:07 builder
2022-06-07 18:34 builder
2022-05-31 15:39 builder
2022-05-18 13:02 builder
2022-05-18 13:45 ` Mark Wielaard
2022-05-18 16:30   ` Luis Machado
2022-05-18  0:23 builder
2022-05-17 10:50 builder
2022-05-17  5:52 builder
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
2022-05-16  9:12       ` Luis Machado

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=20220515002558.E92F13858D32@sourceware.org \
    --to=builder@sourceware.org \
    --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).