From: builder@sourceware.org
To: gcc-rust@gcc.gnu.org
Subject: ☝ Buildbot (Sourceware): gccrust - retry lost connection compile (retry) (master)
Date: Thu, 11 Apr 2024 15:34:40 +0000 [thread overview]
Message-ID: <20240411153440.4CB3C3858CD1@sourceware.org> (raw)
A retry 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/2112
Build state: retry lost connection compile (retry)
Revision: cb64096940cca23dd63f49315fdc1fef7e94b569
Worker: debian-i386
Build Reason: (unknown)
Blamelist: Abdul Rafey <abdulrafeyq@gmail.com>, Arthur Cohen <arthur.cohen@embecosm.com>, Nikos Alexandris <nikos-alexandris@protonmail.com>, Philip Herron <herron.philip@googlemail.com>, Pierre-Emmanuel Patry <pierre-emmanuel.patry@embecosm.com>, goar5670 <mahadelr19@gmail.com>, mxlol233 <mxlol233@outlook.com>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/27/builds/2112/steps/1/logs/stdio
- 2: rm -rf gccrs-build ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/27/builds/2112/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/27/builds/2112/steps/3/logs/stdio
- config.log: https://builder.sourceware.org/buildbot/#/builders/27/builds/2112/steps/3/logs/config_log
- 4: make ( retry )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/27/builds/2112/steps/4/logs/stdio
- cancelled: https://builder.sourceware.org/buildbot/#/builders/27/builds/2112/steps/4/logs/cancelled
next reply other threads:[~2024-04-11 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 15:34 builder [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-11 23:40 builder
2024-04-11 23:40 builder
2023-07-06 17:50 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=20240411153440.4CB3C3858CD1@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).