From: Andreas Enge <andreas@enge.fr>
To: Soren Stoutner <soren@stoutner.com>
Cc: help-guix@gnu.org
Subject: Re: make check never finishes
Date: Mon, 22 May 2023 21:30:23 +0200 [thread overview]
Message-ID: <ZGvCz97GvEfEeRjj@jurong> (raw)
In-Reply-To: <2046910.KbOt5e5Lhv@soren-desktop>
Hello,
Am Mon, May 22, 2023 at 10:54:14AM -0700 schrieb Soren Stoutner via:
> > /gnu/store/6nbb5kb2wj2lja5s77qckvfnabsf786s-sed-tarball-pack.tar.gz.drv
> > /gnu/store/xd5xhbpcgcmy1cvypw4qhag17gbll4lh-profile-directory.drv
> > /gnu/store/s2c4kin834znnc56s4bhy32pqw5vnbiv-profile.drv
> > /gnu/store/g4xjkpaicqmi23nfhp0qhja4c92s5wcz-sed-4.8R.drv
> > /gnu/store/q323ryqh9wa4vinx8d0v3gqmw8lvv119-proot-static-5.3.0.drv
> >
> > building
> > /gnu/store/q323ryqh9wa4vinx8d0v3gqmw8lvv119-proot-static-5.3.0.drv...
> >
> > The CPU hits 100% and stays there for days with no further progress.
I gave it a try, and see the same thing for about the last hour.
There is also a directory
/tmp/guix-build-proot-static-5.3.0.drv-0/
so indeed this package is tried to be built.
I have just interrupted it and then started by hand
guix build /gnu/store/q323ryqh9wa4vinx8d0v3gqmw8lvv119-proot-static-5.3.0.drv
which gives more output.
It does a few tests and then hangs with 100% CPU time after
CHECK test-xxxxxxxx ok
Oh, it is a known issue, see here:
https://issues.guix.gnu.org/63284
Andreas
next prev parent reply other threads:[~2023-05-22 19:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 20:54 make check never finishes Soren Stoutner via
2023-05-22 17:54 ` Soren Stoutner via
2023-05-22 19:30 ` Andreas Enge [this message]
2023-05-22 20:23 ` Soren Stoutner via
-- strict thread matches above, loose matches on Subject: below --
2023-05-17 13:54 Soren Stoutner via
2023-05-17 14:47 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
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=ZGvCz97GvEfEeRjj@jurong \
--to=andreas@enge.fr \
--cc=help-guix@gnu.org \
--cc=soren@stoutner.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).