public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: builder@sourceware.org
To: gcc-rust@gcc.gnu.org
Subject: ☺ Buildbot (GNU Toolchain): gccrust - build successful (master)
Date: Thu, 25 Aug 2022 16:36:14 +0000	[thread overview]
Message-ID: <20220825163614.EBF463852763@sourceware.org> (raw)

A restored build has been detected on builder gccrust-debian-i386 while building gccrust.

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

Build state: build successful
Revision: a3e1361d1ac1ae892d25737e0ee21e71db423a07
Worker: debian-i386-2
Build Reason: (unknown)
Blamelist: Faisal Abbas <90.abbasfaisal@gmail.com>, Philip Herron <philip.herron@embecosm.com>

Steps:

- 0: worker_preparation ( success )

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

- 2: rm -rf gccrs-build ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/368/steps/2/logs/stdio

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

- 4: make ( warnings )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/368/steps/4/logs/stdio
        - warnings (31): https://builder.sourceware.org/buildbot/#builders/27/builds/368/steps/4/logs/warnings__31_

- 5: make check ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/368/steps/5/logs/stdio
        - rust.sum: https://builder.sourceware.org/buildbot/#builders/27/builds/368/steps/5/logs/rust_sum
        - rust.log: https://builder.sourceware.org/buildbot/#builders/27/builds/368/steps/5/logs/rust_log

- 6: grep unexpected rust.sum ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/368/steps/6/logs/stdio

- 7: prep ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/368/steps/7/logs/stdio

- 8: build bunsen.cpio.gz ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/368/steps/8/logs/stdio

- 9: fetch bunsen.cpio.gz ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/368/steps/9/logs/stdio

- 10: unpack bunsen.cpio.gz ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/368/steps/10/logs/stdio

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

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

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

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

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

- 16: rm -rf gccrs-build_1 ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/368/steps/16/logs/stdio


             reply	other threads:[~2022-08-25 16:36 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25 16:36 builder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-15 15:41 builder
2022-12-09 11:12 builder
2022-12-07 16:01 builder
2022-12-07 15:58 builder
2022-12-05  2:17 builder
2022-12-04 23:16 builder
2022-12-04 23:04 builder
2022-12-04 20:20 builder
2022-11-17 11:55 builder
2022-11-17 11:48 builder
2022-11-17 11:28 builder
2022-11-07 14:16 builder
2022-11-01 18:39 builder
2022-10-27 11:05 builder
2022-10-26 15:56 builder
2022-10-21 15:25 builder
2022-10-21 14:04 builder
2022-10-14 15:44 builder
2022-10-07 12:33 builder
2022-09-27 15:33 builder
2022-09-27 15:15 builder
2022-09-27  6:58 builder
2022-09-22 13:55 builder
2022-09-05 12:47 builder
2022-08-31 22:42 builder
2022-08-31 14:23 builder
2022-08-31 11:29 builder
2022-08-31 10:28 builder
2022-08-30 10:51 builder
2022-08-30 10:23 builder
2022-08-26 10:27 builder
2022-08-25 16:39 builder
2022-08-25 16:37 builder
2022-08-19 21:51 builder
2022-08-17 15:29 builder
2022-08-11 14:04 builder
2022-08-10 11:55 builder
2022-08-10 11:53 builder
2022-08-09 15:35 builder
2022-08-08 10:28 builder
2022-08-05 11:21 builder
2022-08-05 11:03 builder
2022-08-05 10:51 builder
2022-08-04 20:47 builder
2022-07-29 17:11 builder
2022-07-27 14:21 builder
2022-07-22 12:03 builder
2022-07-17 20:47 builder
2022-07-07 11:02 builder
2022-07-04 14:58 builder
2022-07-04 14:57 builder
2022-07-04 14:56 builder
2022-06-30 16:42 builder
2022-06-29 10:45 builder
2022-06-24 16:55 builder
2022-06-24  9:48 builder
2022-06-24  9:32 builder
2022-06-24  9:24 builder
2022-05-26 19:47 builder
2022-05-24  1:32 builder
2022-05-20 12:31 builder
2022-05-18 16:29 builder
2022-05-11  9:25 builder
2022-05-09 15:17 builder
2022-05-09 11:45 builder
2022-04-28 20:15 builder
2022-04-26  9:53 builder
2022-04-22 14:37 builder
2022-04-22 13:53 builder
2022-04-21 20:45 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=20220825163614.EBF463852763@sourceware.org \
    --to=builder@sourceware.org \
    --cc=gcc-rust@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: 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).