unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Tom Fitzhenry" <tom@tom-fitzhenry.me.uk>
To: "Maxim Cournoyer" <maxim.cournoyer@gmail.com>
Cc: Mathieu Othacehe <othacehe@gnu.org>, 55848@debbugs.gnu.org
Subject: bug#55848: [cuirass] workers stalled
Date: Mon, 20 Jun 2022 12:44:38 +1000	[thread overview]
Message-ID: <173fb399-9db1-40de-b8bc-662f1f1736d2@www.fastmail.com> (raw)
In-Reply-To: <878rps83ec.fsf@gmail.com>

On Mon, 20 Jun 2022, at 12:39 PM, Maxim Cournoyer wrote:
> That's a known issue with mrustc; it only succeeds with x86_64; the
> other architectures have problems.  That's a bug the mrustc author would
> like to fix, so perhaps in time in will improve (especially if
> interested parties can lend a hand).

mrustc was fixed on aarch64 in https://issues.guix.gnu.org/54580 on staging, which was recently merged to master.

I had tested mrustc and rust-1.39 to compile on aarch64 on staging, but now I observe rust-1.39 failing.

I'll take a closer look, maybe I'm missing something.




  reply	other threads:[~2022-06-20  2:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 15:31 bug#55848: [cuirass] workers stalled Mathieu Othacehe
2022-06-08 19:07 ` Greg Hogan
2022-06-11 10:44   ` Tom Fitzhenry
2022-06-12 13:33     ` Ludovic Courtès
2022-06-12 16:10       ` Ricardo Wurmus
2022-06-12 20:22         ` Ludovic Courtès
2022-08-10 13:46       ` bug#55848: AArch64 honeycomb machines aren’t building stuff Ludovic Courtès
2022-08-10 17:55         ` Ricardo Wurmus
2022-08-11 14:06           ` bug#55848: [cuirass] workers stalled Ludovic Courtès
2022-08-29 13:30         ` bug#55848: AArch64 Honeycomb builders are inactive Ludovic Courtès
2022-06-19  2:07 ` bug#55848: [cuirass] workers stalled Tom Fitzhenry
2022-06-20  2:39   ` Maxim Cournoyer
2022-06-20  2:44     ` Tom Fitzhenry [this message]
2022-06-20 13:02     ` Maxime Devos
2022-06-21  5:32       ` Maxim Cournoyer

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=173fb399-9db1-40de-b8bc-662f1f1736d2@www.fastmail.com \
    --to=tom@tom-fitzhenry.me.uk \
    --cc=55848@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=othacehe@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).