From: builder@sourceware.org
To: dwz@sourceware.org
Subject: ☺ Buildbot (GNU Toolchain): dwz - build successful (master)
Date: Thu, 07 Jul 2022 12:46:06 +0000 [thread overview]
Message-ID: <20220707124606.98D573857B99@sourceware.org> (raw)
A restored build has been detected on builder dwz-debian-amd64 while building dwz.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/50/builds/11
Build state: build successful
Revision: bb44ff3ab1a45ac19588ebc97966e6774d0e018b
Worker: bb2
Build Reason: (unknown)
Blamelist: Martin Liska <mliska@suse.cz>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/50/builds/11/steps/1/logs/stdio
- 2: make ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/50/builds/11/steps/2/logs/stdio
- 3: make check ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/50/builds/11/steps/3/logs/stdio
- dwz.sum: https://builder.sourceware.org/buildbot/#builders/50/builds/11/steps/3/logs/dwz_sum
- dwz.log: https://builder.sourceware.org/buildbot/#builders/50/builds/11/steps/3/logs/dwz_log
- 4: prep ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/50/builds/11/steps/4/logs/stdio
- 5: fetch ['dwz.sum', 'dwz.log'] ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/50/builds/11/steps/5/logs/stdio
- 6: pass .bunsen.source.gitname ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/50/builds/11/steps/6/logs/stdio
- 7: pass .bunsen.source.gitbranch ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/50/builds/11/steps/7/logs/stdio
- 8: pass .bunsen.source.gitrepo ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/50/builds/11/steps/8/logs/stdio
- 9: upload to bunsen ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/50/builds/11/steps/9/logs/stdio
- 10: clean up ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/50/builds/11/steps/10/logs/stdio
next reply other threads:[~2022-07-07 12:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 12:46 builder [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-03 22:18 builder
2022-07-11 8:44 builder
2022-07-11 8:44 builder
2022-07-07 15:29 builder
2022-07-07 13:12 builder
2022-07-07 13:10 builder
2022-07-07 12:46 builder
2022-07-07 12:39 builder
2022-07-07 12:38 builder
2022-07-07 12:32 builder
2022-07-07 12:31 builder
2022-07-01 7:56 builder
2022-06-30 12:50 builder
2022-06-30 12:55 ` Mark Wielaard
2022-06-25 21:56 builder
2022-06-25 22:17 ` Mark Wielaard
2022-06-27 7:25 ` Martin Liška
2022-06-28 21:43 ` Mark Wielaard
2022-06-29 7:17 ` Florian Weimer
2022-06-30 14:23 ` Martin Liška
2022-06-30 20:05 ` Mark Wielaard
2022-07-01 6:42 ` Martin Liška
2022-07-01 7:43 ` Mark Wielaard
2022-07-01 7:53 ` Martin Liška
2022-06-25 21:55 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=20220707124606.98D573857B99@sourceware.org \
--to=builder@sourceware.org \
--cc=dwz@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).