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 (Sourceware): gccrust - build successful (master)
Date: Thu, 23 Feb 2023 22:21:14 +0000	[thread overview]
Message-ID: <20230223222114.D5891385840F@sourceware.org> (raw)

A passing build has been detected on builder gccrust-opensusetw-x86_64 while building gccrust.

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

Build state: build successful
Revision: aedd97a537cbf12ad775504a71e5901ea2dacdad
Worker: bb1-2
Build Reason: (unknown)
Blamelist: Arthur Cohen <arthur.cohen@embecosm.com>, Jakub Dupak <dev@jakubdupak.com>

Steps:

- 0: worker_preparation ( success )

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

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

- 3: configure ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/665/steps/3/logs/stdio
        - config.log: https://builder.sourceware.org/buildbot/#builders/103/builds/665/steps/3/logs/config_log

- 4: make ( warnings )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/665/steps/4/logs/stdio
        - warnings (33): https://builder.sourceware.org/buildbot/#builders/103/builds/665/steps/4/logs/warnings__33_

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

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

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

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

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

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

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

- 12: pass .bunsen.source.gitdescribe ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/665/steps/12/logs/stdio

- 13: pass .bunsen.source.gitbranch ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/665/steps/13/logs/stdio

- 14: pass .bunsen.source.gitrepo ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/665/steps/14/logs/stdio

- 15: upload to bunsen ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/665/steps/15/logs/stdio

- 16: clean up ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/665/steps/16/logs/stdio

- 17: rm -rf gccrs-build_1 ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/665/steps/17/logs/stdio


             reply	other threads:[~2023-02-23 22:21 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23 22:21 builder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-25 10:06 builder
2024-03-25 10:00 builder
2024-03-25  9:06 builder
2024-03-25  8:51 builder
2024-03-12 12:56 builder
2024-03-12 11:25 builder
2024-02-29 14:18 builder
2024-02-29 14:09 builder
2023-12-27 14:20 builder
2023-12-19 19:06 builder
2023-10-26 17:37 builder
2023-09-11 16:32 builder
2023-09-03 19:46 builder
2023-08-28 21:07 builder
2023-08-18 22:09 builder
2023-08-18 20:41 builder
2023-08-18 15:53 builder
2023-08-18 16:05 ` Mark Wielaard
2023-08-09 13:44 builder
2023-07-31 14:25 builder
2023-07-14 18:17 builder
2023-06-21 10:17 builder
2023-06-20  9:59 builder
2023-06-01 10:04 builder
2023-05-30 17:44 builder
2023-05-30  9:46 builder
2023-05-26 18:08 builder
2023-05-11  9:48 builder
2023-05-11  9:31 builder
2023-05-11  9:15 builder
2023-05-11  9:07 builder
2023-05-08 16:23 builder
2023-04-27 23:41 builder
2023-04-26 23:21 builder
2023-04-26 17:43 builder
2023-04-26 17:22 builder
2023-04-14 13:51 builder
2023-04-13 13:05 builder
2023-04-11 14:16 builder
2023-04-10  9:46 builder
2023-04-05 10:55 builder
2023-04-04 13:25 builder
2023-03-25  9:54 builder
2023-03-20 23:28 builder
2023-03-17 18:02 builder
2023-02-28 22:32 builder
2023-02-28 22:06 builder
2023-02-24  2:14 builder
2023-02-24  1:59 builder
2023-02-24  1:20 builder
2023-02-24  1:05 builder
2023-02-24  0:53 builder
2023-02-24  0:11 builder
2023-02-23 22:56 builder
2023-02-23 21:24 builder
2023-02-23 20:23 builder
2023-02-23 20:08 builder
2023-02-23 18:00 builder
2023-02-23 17:33 builder
2023-02-13 22:08 builder
2023-02-13 20:27 builder
2023-02-13 20:11 builder
2023-02-13 15:00 builder
2023-02-13 12:53 builder
2023-02-13 12:51 builder
2023-02-10 11:33 builder
2023-02-02 22:49 builder
2023-02-02 22:48 builder
2023-01-26 16:34 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=20230223222114.D5891385840F@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).