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 - cancelled compile (cancelled) (master)
Date: Thu, 25 Aug 2022 16:36:26 +0000	[thread overview]
Message-ID: <20220825163626.5E774385AC11@sourceware.org> (raw)

A cancelled build has been detected on builder gccrust-fedora-x86_64 while building gccrust.

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

Build state: cancelled compile (cancelled)
Revision: f21f475feca30d0c9fb74dfe3bb65a6d88d5311c
Worker: bbo1-2
Build Reason: (unknown)
Blamelist: Faisal Abbas <90.abbasfaisal@gmail.com>

Steps:

- 0: worker_preparation ( success )

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

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

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

- 4: make ( cancelled )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/350/steps/4/logs/stdio
        - cancelled: https://builder.sourceware.org/buildbot/#builders/16/builds/350/steps/4/logs/cancelled
        - warnings (7): https://builder.sourceware.org/buildbot/#builders/16/builds/350/steps/4/logs/warnings__7_


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

Thread overview: 2+ 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-08-25 16:36 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=20220825163626.5E774385AC11@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).