public inbox for gdbadmin@sourceware.org
help / color / mirror / Atom feed
From: builder@sourceware.org
To: "GDB Administrator" <gdbadmin@sourceware.org>
Subject: ☠ Buildbot (Sourceware): binutils-gdb - failed compile (failure) (master)
Date: Mon, 01 May 2023 05:55:21 +0000	[thread overview]
Message-ID: <20230501055521.722CD3858D39@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/3847

Build state: failed compile (failure)
Revision: 077a1f08485e88f3b234af1dbb8b907b16045e6a
Worker: bbo1-1
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/3847/steps/1/logs/stdio

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

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

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

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

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

Build state: failed compile (failure)
Revision: 077a1f08485e88f3b234af1dbb8b907b16045e6a
Worker: bb2-1
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/97/builds/3566/steps/1/logs/stdio

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

- 3: configure ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/97/builds/3566/steps/3/logs/stdio
        - config.log: https://builder.sourceware.org/buildbot/#builders/97/builds/3566/steps/3/logs/config_log

- 4: make ( failure )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/97/builds/3566/steps/4/logs/stdio
        - warnings (186): https://builder.sourceware.org/buildbot/#builders/97/builds/3566/steps/4/logs/warnings__186_


             reply	other threads:[~2023-05-01  5:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-01  5:55 builder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-23 18:52 builder
2024-01-29 19:38 builder
2024-01-22  0:59 builder
2023-07-19  0:43 builder
2023-05-02 16:24 builder
2023-04-27  0:36 builder
2023-04-24  0:31 builder
2023-04-24  0:29 builder
2023-04-14  0:30 builder
2023-04-07  0:28 builder
2023-04-06  0:46 builder
2023-03-20  8:45 builder
2023-03-06  0:28 builder
2023-02-17  1:11 builder
2023-01-19  0:23 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=20230501055521.722CD3858D39@sourceware.org \
    --to=builder@sourceware.org \
    --cc=gdbadmin@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).