From: builder@sourceware.org
To: "Ben Woodard" <woodard@redhat.com>,
"Guillermo E. Martinez via Libabigail"
<libabigail@sourceware.org>
Cc: libabigail@sourceware.org
Subject: ☺ Buildbot (GNU Toolchain): libabigail - build successful (master)
Date: Mon, 02 May 2022 16:30:12 +0000 [thread overview]
Message-ID: <20220502163012.D05263858C50@sourceware.org> (raw)
A restored build has been detected on builder libabigail-fedora-ppc64 while building libabigail.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/51/builds/2
Build state: build successful
Revision: f52c0ba41654a5ea7baa1be4fdaaefa18a94ae47
Worker: fedora-ppc64
Build Reason: (unknown)
Blamelist: Ben Woodard <woodard@redhat.com>, Guillermo E. Martinez via Libabigail <libabigail@sourceware.org>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/51/builds/2/steps/1/logs/stdio
- 2: autoreconf ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/51/builds/2/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/51/builds/2/steps/3/logs/stdio
- 4: make ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/51/builds/2/steps/4/logs/stdio
- 5: make check ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/51/builds/2/steps/5/logs/stdio
- test-suite.log: https://builder.sourceware.org/buildbot/#builders/51/builds/2/steps/5/logs/test-suite_log
- 6: prep ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/51/builds/2/steps/6/logs/stdio
- 7: fetch ['tests/*.trs', 'tests/*.log'] ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/51/builds/2/steps/7/logs/stdio
- 8: fetch ['libabigail-*/_build/sub/tests/*.trs', 'lib ( skipped )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/51/builds/2/steps/8/logs/stdio
- 9: fetch ['config.log'] ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/51/builds/2/steps/9/logs/stdio
- 10: fetch ['libabigail-*/_build/sub/config.log'] ( skipped )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/51/builds/2/steps/10/logs/stdio
- 11: pass .bunsen.source.gitname ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/51/builds/2/steps/11/logs/stdio
- 12: pass .bunsen.source.gitrepo ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/51/builds/2/steps/12/logs/stdio
- 13: upload to bunsen ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/51/builds/2/steps/13/logs/stdio
- 14: clean up ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/51/builds/2/steps/14/logs/stdio
A restored build has been detected on builder libabigail-debian-ppc64 while building libabigail.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/67/builds/2
Build state: build successful
Revision: f52c0ba41654a5ea7baa1be4fdaaefa18a94ae47
Worker: debian-ppc64
Build Reason: (unknown)
Blamelist: Ben Woodard <woodard@redhat.com>, Guillermo E. Martinez via Libabigail <libabigail@sourceware.org>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/67/builds/2/steps/1/logs/stdio
- 2: autoreconf ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/67/builds/2/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/67/builds/2/steps/3/logs/stdio
- 4: make ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/67/builds/2/steps/4/logs/stdio
- 5: make check ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/67/builds/2/steps/5/logs/stdio
- test-suite.log: https://builder.sourceware.org/buildbot/#builders/67/builds/2/steps/5/logs/test-suite_log
- 6: prep ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/67/builds/2/steps/6/logs/stdio
- 7: fetch ['tests/*.trs', 'tests/*.log'] ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/67/builds/2/steps/7/logs/stdio
- 8: fetch ['libabigail-*/_build/sub/tests/*.trs', 'lib ( skipped )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/67/builds/2/steps/8/logs/stdio
- 9: fetch ['config.log'] ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/67/builds/2/steps/9/logs/stdio
- 10: fetch ['libabigail-*/_build/sub/config.log'] ( skipped )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/67/builds/2/steps/10/logs/stdio
- 11: pass .bunsen.source.gitname ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/67/builds/2/steps/11/logs/stdio
- 12: pass .bunsen.source.gitrepo ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/67/builds/2/steps/12/logs/stdio
- 13: upload to bunsen ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/67/builds/2/steps/13/logs/stdio
- 14: clean up ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/67/builds/2/steps/14/logs/stdio
next reply other threads:[~2022-05-02 16:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 16:30 builder [this message]
2022-05-03 11:11 ` Mark Wielaard
2022-05-30 9:16 builder
2022-06-09 10:40 builder
2022-06-15 14:04 builder
2022-06-18 20:11 builder
2022-06-23 14:12 builder
2022-07-01 13:16 builder
2022-07-18 22:12 builder
2022-07-19 17:07 builder
2022-07-23 0:12 builder
2022-07-24 16:42 builder
2022-09-05 16:12 builder
2022-09-13 9:45 builder
2022-09-20 8:07 builder
2022-09-26 6:58 builder
2022-10-10 12:19 builder
2022-11-30 16:58 builder
2022-12-19 17:49 builder
2022-12-19 17:49 builder
2022-12-19 18:19 builder
2023-01-06 21: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=20220502163012.D05263858C50@sourceware.org \
--to=builder@sourceware.org \
--cc=libabigail@sourceware.org \
--cc=woodard@redhat.com \
/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).