public inbox for gcc-testresults@sourceware.org help / color / mirror / Atom feed
From: builder@sourceware.org To: gcc-testresults@gcc.gnu.org Subject: ☺ Buildbot (GNU Toolchain): gcc - build successful (master) Date: Tue, 06 Dec 2022 14:09:57 +0000 [thread overview] Message-ID: <20221206140957.4963E3864A3B@sourceware.org> (raw) A passing build has been detected on builder gcc-debian-amd64 while building gcc. Full details are available at: https://builder.sourceware.org/buildbot/#builders/154/builds/2357 Build state: build successful Revision: 400d9fc1f04336118c3200e2af14a620e7ea1d95 Worker: bb1-2 Build Reason: (unknown) Blamelist: Eric Botcazou <ebotcazou@adacore.com>, Javier Miranda <miranda@adacore.com>, Justin Squirek <squirek@adacore.com>, Yannick Moy <moy@adacore.com> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/154/builds/2357/steps/1/logs/stdio - 2: rm -rf gcc-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/154/builds/2357/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/154/builds/2357/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/154/builds/2357/steps/4/logs/stdio - warnings (94): https://builder.sourceware.org/buildbot/#builders/154/builds/2357/steps/4/logs/warnings__94_ - 5: rm -rf gcc-build_1 ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/154/builds/2357/steps/5/logs/stdio
next reply other threads:[~2022-12-06 14:09 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-06 14:09 builder [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-01-16 0:01 builder 2022-12-27 20:56 builder 2022-12-24 0:18 builder 2022-12-22 17:21 builder 2022-12-21 3:19 builder 2022-12-19 20:53 builder 2022-12-19 14:31 builder 2022-12-16 21:12 builder 2022-12-09 2:32 builder 2022-12-08 11:07 builder 2022-12-06 18:39 builder 2022-12-02 21:41 builder 2022-12-01 16:20 builder 2022-11-30 1:11 builder 2022-11-28 9:25 builder 2022-11-28 3:14 builder 2022-11-26 0:37 builder 2022-11-25 10:12 builder 2022-11-24 8:18 builder 2022-11-23 2:34 builder 2022-11-23 2:10 builder 2022-11-22 23:52 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=20221206140957.4963E3864A3B@sourceware.org \ --to=builder@sourceware.org \ --cc=gcc-testresults@gcc.gnu.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: linkBe 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).