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 compile (failure) (master)
Date: Thu, 09 Jun 2022 00:26:48 +0000	[thread overview]
Message-ID: <20220609002648.72EB1386CE51@sourceware.org> (raw)

A new failure has been detected on builder gdb-fedora-x86_64 while building binutils-gdb.

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

Build state: failed compile (failure)
Revision: d21691eaa7e851a7600ce1f616c5289b7c69055b
Worker: bb3
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/74/builds/435/steps/1/logs/stdio

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

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

- 4: make ( failure )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/74/builds/435/steps/4/logs/stdio
        - warnings (4): https://builder.sourceware.org/buildbot/#builders/74/builds/435/steps/4/logs/warnings__4_



             reply	other threads:[~2022-06-09  0:26 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09  0:26 builder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-15 23:45 builder
2023-01-15 23:58 ` Mark Wielaard
2023-01-16  0:40   ` Mike Frysinger
2023-01-15  3:18 builder
2023-01-14  3:21 builder
2023-01-14  3:00 builder
2023-01-13 22:44 builder
2023-01-12  7:18 builder
2023-01-09 23:59 builder
2023-01-09 23:48 builder
2023-01-02 17:28 builder
2022-12-21 17:26 builder
2022-12-13 16:21 builder
2022-12-06 15:08 builder
2022-12-06 15:08 builder
2022-11-18 16:27 builder
2022-11-07 20:08 builder
2022-11-05 14:01 builder
2022-11-01 10:00 builder
2022-10-24 17:55 builder
2022-10-21 18:43 builder
2022-10-20  5:17 builder
2022-10-19  9:39 builder
2022-10-19  0:24 builder
2022-10-16 19:15 builder
2022-10-16 18:54 builder
2022-10-16 18:22 builder
2022-10-16 18:04 builder
2022-10-16 17:26 builder
2022-08-08  3:31 builder
2022-08-04 20:09 builder
2022-07-21 19:11 builder
2022-07-20 19:26 builder
2022-07-14  6:40 builder
2022-07-12 10:44 builder
2022-06-27 23:03 builder
2022-06-27 23:54 ` Mark Wielaard
2022-06-17 10:13 builder
2022-06-13  8:19 builder
     [not found] <20220609002024.1DF6B3853547@sourceware.org>
     [not found] ` <CAG_eJLfRrgsK62e7UX_HF7p5O+czBnTm6z+8K=KnDsasadkp5Q@mail.gmail.com>
2022-06-09  3:36   ` Mark Wielaard
2022-05-16 16:13 builder
2022-05-04 13:49 builder
2022-05-03 23:21 builder
2022-04-30  3:34 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=20220609002648.72EB1386CE51@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).