public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: builder@sourceware.org
To: elfutils-devel@sourceware.org
Subject: ☺ Buildbot (GNU Toolchain): elfutils - build successful (master)
Date: Thu, 27 Oct 2022 14:11:21 +0000	[thread overview]
Message-ID: <20221027141121.752403851508@sourceware.org> (raw)

A restored build has been detected on builder elfutils-fedora-x86_64 while building elfutils.

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

Build state: build successful
Revision: eae6ad37f96826b1b7ddf269ee4d753079054413
Worker: bbo1-1
Build Reason: (unknown)
Blamelist: Frank Ch. Eigler <fche@redhat.com>, Yonggang Luo <luoyonggang@gmail.com>

Steps:

- 0: worker_preparation ( success )

- 1: set package name ( success )

- 2: git checkout ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/2/logs/stdio

- 3: autoreconf ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/3/logs/stdio

- 4: configure ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/4/logs/stdio

- 5: get version ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/5/logs/stdio
        - property changes: https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/5/logs/property_changes

- 6: make ( warnings )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/6/logs/stdio
        - warnings (3): https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/6/logs/warnings__3_

- 7: make check ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/7/logs/stdio
        - test-suite.log: https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/7/logs/test-suite_log

- 8: make distcheck ( warnings )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/8/logs/stdio
        - test-suite.log: https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/8/logs/test-suite_log
        - warnings (6): https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/8/logs/warnings__6_

- 9: prep ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/9/logs/stdio

- 10: build bunsen.cpio.gz ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/10/logs/stdio

- 11: fetch bunsen.cpio.gz ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/11/logs/stdio

- 12: unpack bunsen.cpio.gz ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/12/logs/stdio

- 13: pass .bunsen.source.gitname ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/13/logs/stdio

- 14: pass .bunsen.source.gitdescribe ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/14/logs/stdio

- 15: pass .bunsen.source.gitbranch ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/15/logs/stdio

- 16: pass .bunsen.source.gitrepo ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/16/logs/stdio

- 17: upload to bunsen ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/17/logs/stdio

- 18: clean up ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/18/logs/stdio

- 19: make distclean ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/59/builds/88/steps/19/logs/stdio


             reply	other threads:[~2022-10-27 14:11 UTC|newest]

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