From: Greg Hogan <code@greghogan.com>
To: Soren Stoutner <soren@stoutner.com>
Cc: help-guix@gnu.org, Simon Tournier <zimon.toutoune@gmail.com>
Subject: Re: make check never finishes
Date: Tue, 23 May 2023 15:16:12 -0400 [thread overview]
Message-ID: <CA+3U0ZkOAN2bv8AfYoE9iKcyEzZuy6npmKmjic3myL7rjLSRXA@mail.gmail.com> (raw)
In-Reply-To: <4a4659cc90aaab148dad3fe754f98a7b@stoutner.com>
On Tue, May 23, 2023 at 1:23 PM Soren Stoutner via <help-guix@gnu.org> wrote:
>
> I just tried it again with 6783f558fa2bcbc662e021e1b3bf502c64706177 and
> had the same issue.
proot-static fails to build. The issue has been reported upstream.
https://github.com/proot-me/proot/issues/352
The recent 5.4.0 release fixes the hung tests but the previous issue
is still outstanding.
https://github.com/proot-me/proot/commit/a5ee0b79001d4ca338a74b4259d12ad9e40a3a38
One workaround is to checkout the Guix source and configure a
development environment, disabling the proot tests locally. I
understand that this broken test may indicate a regression, but there
must be a better path forward than allowing this to linger for months
breaking Guix functionality.
next prev parent reply other threads:[~2023-05-23 19:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 14:47 make check never finishes Soren Stoutner via
2023-05-17 15:40 ` Sergiu Ivanov
2023-05-17 16:12 ` Soren Stoutner via
2023-05-23 10:19 ` Simon Tournier
2023-05-23 13:27 ` Soren Stoutner via
2023-05-23 17:22 ` Soren Stoutner via
2023-05-23 19:16 ` Greg Hogan [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-17 13:54 Soren Stoutner via
2023-05-16 20:54 Soren Stoutner via
2023-05-22 17:54 ` Soren Stoutner via
2023-05-22 19:30 ` Andreas Enge
2023-05-22 20:23 ` Soren Stoutner via
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=CA+3U0ZkOAN2bv8AfYoE9iKcyEzZuy6npmKmjic3myL7rjLSRXA@mail.gmail.com \
--to=code@greghogan.com \
--cc=help-guix@gnu.org \
--cc=soren@stoutner.com \
--cc=zimon.toutoune@gmail.com \
/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).