public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: builder@sourceware.org
To: binutils@sourceware.org
Subject: ☺ Buildbot (GNU Toolchain): binutils-gdb - build successful (master)
Date: Sun, 17 Jul 2022 00:13:53 +0000	[thread overview]
Message-ID: <20220717001353.62E563858404@sourceware.org> (raw)

A restored build has been detected on builder binutils-debian-amd64 while building binutils-gdb.

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

Build state: build successful
Revision: f39cc214d560a5fac30f64c9ef2d0daeeab9f901
Worker: bb3
Build Reason: (unknown)
Blamelist: Aaron Merey <amerey@redhat.com>, Bruno Larsen <blarsen@redhat.com>, Carl Love <cel@us.ibm.com>, GDB Administrator <gdbadmin@sourceware.org>, Tom Tromey <tromey@adacore.com>

Steps:

- 0: worker_preparation ( success )

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

- 2: rm -rf binutils-build ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/366/steps/2/logs/stdio

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

- 4: make ( warnings )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/366/steps/4/logs/stdio
        - warnings (20): https://builder.sourceware.org/buildbot/#builders/68/builds/366/steps/4/logs/warnings__20_

- 5: make check ( warnings )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/366/steps/5/logs/stdio
        - ld.sum: https://builder.sourceware.org/buildbot/#builders/68/builds/366/steps/5/logs/ld_sum
        - ld.log: https://builder.sourceware.org/buildbot/#builders/68/builds/366/steps/5/logs/ld_log
        - gas.sum: https://builder.sourceware.org/buildbot/#builders/68/builds/366/steps/5/logs/gas_sum
        - gas.log: https://builder.sourceware.org/buildbot/#builders/68/builds/366/steps/5/logs/gas_log
        - binutils.sum: https://builder.sourceware.org/buildbot/#builders/68/builds/366/steps/5/logs/binutils_sum
        - binutils.log: https://builder.sourceware.org/buildbot/#builders/68/builds/366/steps/5/logs/binutils_log
        - warnings (6): https://builder.sourceware.org/buildbot/#builders/68/builds/366/steps/5/logs/warnings__6_

- 6: prep ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/366/steps/6/logs/stdio

- 7: build bunsen.cpio ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/366/steps/7/logs/stdio

- 8: fetch bunsen.cpio ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/366/steps/8/logs/stdio

- 9: unpack bunsen.cpio ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/366/steps/9/logs/stdio

- 10: pass .bunsen.source.gitname ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/366/steps/10/logs/stdio

- 11: pass .bunsen.source.gitbranch ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/366/steps/11/logs/stdio

- 12: pass .bunsen.source.gitrepo ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/366/steps/12/logs/stdio

- 13: upload to bunsen ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/366/steps/13/logs/stdio

- 14: clean up ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/366/steps/14/logs/stdio

A restored build has been detected on builder binutils-debian-testing-x86_64 while building binutils-gdb.

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

Build state: build successful
Revision: f39cc214d560a5fac30f64c9ef2d0daeeab9f901
Worker: bb1
Build Reason: (unknown)
Blamelist: Aaron Merey <amerey@redhat.com>, Bruno Larsen <blarsen@redhat.com>, Carl Love <cel@us.ibm.com>, GDB Administrator <gdbadmin@sourceware.org>, Tom Tromey <tromey@adacore.com>

Steps:

- 0: worker_preparation ( success )

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

- 2: rm -rf binutils-build ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/149/builds/75/steps/2/logs/stdio

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

- 4: make ( warnings )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/149/builds/75/steps/4/logs/stdio
        - warnings (24): https://builder.sourceware.org/buildbot/#builders/149/builds/75/steps/4/logs/warnings__24_

- 5: make check ( warnings )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/149/builds/75/steps/5/logs/stdio
        - ld.sum: https://builder.sourceware.org/buildbot/#builders/149/builds/75/steps/5/logs/ld_sum
        - ld.log: https://builder.sourceware.org/buildbot/#builders/149/builds/75/steps/5/logs/ld_log
        - gas.sum: https://builder.sourceware.org/buildbot/#builders/149/builds/75/steps/5/logs/gas_sum
        - gas.log: https://builder.sourceware.org/buildbot/#builders/149/builds/75/steps/5/logs/gas_log
        - binutils.sum: https://builder.sourceware.org/buildbot/#builders/149/builds/75/steps/5/logs/binutils_sum
        - binutils.log: https://builder.sourceware.org/buildbot/#builders/149/builds/75/steps/5/logs/binutils_log
        - libctf.sum: https://builder.sourceware.org/buildbot/#builders/149/builds/75/steps/5/logs/libctf_sum
        - libctf.log: https://builder.sourceware.org/buildbot/#builders/149/builds/75/steps/5/logs/libctf_log
        - warnings (8): https://builder.sourceware.org/buildbot/#builders/149/builds/75/steps/5/logs/warnings__8_

- 6: prep ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/149/builds/75/steps/6/logs/stdio

- 7: build bunsen.cpio ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/149/builds/75/steps/7/logs/stdio

- 8: fetch bunsen.cpio ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/149/builds/75/steps/8/logs/stdio

- 9: unpack bunsen.cpio ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/149/builds/75/steps/9/logs/stdio

- 10: pass .bunsen.source.gitname ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/149/builds/75/steps/10/logs/stdio

- 11: pass .bunsen.source.gitbranch ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/149/builds/75/steps/11/logs/stdio

- 12: pass .bunsen.source.gitrepo ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/149/builds/75/steps/12/logs/stdio

- 13: upload to bunsen ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/149/builds/75/steps/13/logs/stdio

- 14: clean up ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/149/builds/75/steps/14/logs/stdio


             reply	other threads:[~2022-07-17  0:13 UTC|newest]

Thread overview: 98+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-17  0:13 builder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-10 11:00 builder
2023-01-05  8:52 builder
2022-12-25  8:37 builder
2022-12-17  1:20 builder
2022-12-16 16:03 builder
2022-12-12 18:13 builder
2022-12-12 13:11 builder
2022-12-12  9:14 builder
2022-12-12  8:06 builder
2022-12-07  6:17 builder
2022-11-30 16:44 builder
2022-11-30 16:34 builder
2022-11-30  8:59 builder
2022-11-28 10:22 builder
2022-11-28  3:03 builder
2022-11-21 17:07 builder
2022-11-16  1:51 builder
2022-11-11  7:55 builder
2022-11-07  5:16 builder
2022-11-02  3:13 builder
2022-11-01 11:05 builder
2022-10-31 16:30 builder
2022-10-24  8:00 builder
2022-10-20  0:15 builder
2022-10-19 12:57 builder
2022-10-19 11:47 builder
2022-10-11 13:48 builder
2022-10-06  4:41 builder
2022-10-06  4:00 builder
2022-10-05  7:34 builder
2022-10-05  4:41 builder
2022-10-04 13:52 builder
2022-10-04  8:25 builder
2022-10-03 12:21 builder
2022-09-30  4:24 builder
2022-09-29  0:23 builder
2022-09-28 12:14 builder
2022-09-28  4:48 builder
2022-09-27  5:53 builder
2022-09-27  4:02 builder
2022-09-27  0:18 builder
2022-09-26 15:44 builder
2022-09-26 10:14 builder
2022-09-26  6:03 builder
2022-09-24  2:26 builder
2022-09-22 17:50 builder
2022-09-22 17:30 builder
2022-09-22  7:32 builder
2022-09-20 11:21 builder
2022-09-14  6:00 builder
2022-09-14  0:18 builder
2022-09-08 12:05 builder
2022-09-06 16:03 builder
2022-09-06  2:46 builder
2022-09-02 17:32 builder
2022-09-02  6:42 builder
2022-08-30 15:35 builder
2022-08-28  0:19 builder
2022-08-25 10:55 builder
2022-08-24 16:25 builder
2022-08-23  9:11 builder
2022-08-23  8:53 builder
2022-08-22  9:41 builder
2022-08-20 22:44 builder
2022-08-16  8:02 builder
2022-08-16  7:36 builder
2022-08-14  0:15 builder
2022-08-11  9:34 builder
2022-08-09  8:00 builder
2022-08-06 10:06 builder
2022-08-05 11:48 builder
2022-08-01  4:59 builder
2022-07-26 13:26 builder
2022-07-26 13:06 builder
2022-07-21 22:45 builder
2022-07-19 16:01 builder
2022-07-19  2:09 builder
2022-07-08 11:54 builder
2022-07-04 11:41 builder
2022-07-03 16:50 builder
2022-07-03 16:45 builder
2022-06-29 17:01 builder
2022-06-28  1:46 builder
2022-06-27 13:52 builder
2022-06-27  3:18 builder
2022-06-25  0:19 builder
2022-06-21 19:22 builder
2022-06-13  9:36 builder
2022-06-09  4:02 builder
2022-06-09  3:48 builder
2022-06-09 13:18 ` Mark Wielaard
2022-06-02 11:18 builder
2022-06-02  9:44 builder
2022-05-30  8:02 builder
2022-05-30  7:56 builder
2022-05-25 23:53 builder
2022-05-19 11:11 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=20220717001353.62E563858404@sourceware.org \
    --to=builder@sourceware.org \
    --cc=binutils@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).