public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: builder@sourceware.org
To: libabigail@sourceware.org
Subject: ☺ Buildbot (GNU Toolchain): libabigail - build successful (master)
Date: Fri, 01 Jul 2022 13:16:15 +0000	[thread overview]
Message-ID: <20220701131615.88B473857BB4@sourceware.org> (raw)

A restored build has been detected on builder libabigail-fedora-ppc64le while building libabigail.

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

Build state: build successful
Revision: 7e18fc8ad8c00db49e8889f28198bfdcedeb4a03
Worker: fedora-ppc64le
Build Reason: (unknown)
Blamelist: Giuliano Procida <gprocida@google.com>

Steps:

- 0: worker_preparation ( success )

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

- 2: autoreconf ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/38/builds/46/steps/2/logs/stdio

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

- 4: make ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/38/builds/46/steps/4/logs/stdio

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

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

- 7: fetch ['tests/*.trs', 'tests/*.log'] ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/38/builds/46/steps/7/logs/stdio

- 8: fetch ['libabigail-*/_build/sub/tests/*.trs', 'lib ( skipped )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/38/builds/46/steps/8/logs/stdio

- 9: fetch ['config.log'] ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/38/builds/46/steps/9/logs/stdio

- 10: fetch ['libabigail-*/_build/sub/config.log'] ( skipped )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/38/builds/46/steps/10/logs/stdio

- 11: pass .bunsen.source.gitname ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/38/builds/46/steps/11/logs/stdio

- 12: pass .bunsen.source.gitbranch ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/38/builds/46/steps/12/logs/stdio

- 13: pass .bunsen.source.gitrepo ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/38/builds/46/steps/13/logs/stdio

- 14: upload to bunsen ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/38/builds/46/steps/14/logs/stdio

- 15: clean up ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/38/builds/46/steps/15/logs/stdio


             reply	other threads:[~2022-07-01 13:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01 13:16 builder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-06 21:23 builder
2022-12-19 18:19 builder
2022-12-19 17:49 builder
2022-12-19 17:49 builder
2022-11-30 16:58 builder
2022-10-10 12:19 builder
2022-09-26  6:58 builder
2022-09-20  8:07 builder
2022-09-13  9:45 builder
2022-09-05 16:12 builder
2022-07-24 16:42 builder
2022-07-23  0:12 builder
2022-07-19 17:07 builder
2022-07-18 22:12 builder
2022-06-23 14:12 builder
2022-06-18 20:11 builder
2022-06-15 14:04 builder
2022-06-09 10:40 builder
2022-05-30  9:16 builder
2022-05-02 16:30 builder
2022-05-03 11:11 ` Mark Wielaard

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=20220701131615.88B473857BB4@sourceware.org \
    --to=builder@sourceware.org \
    --cc=libabigail@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).