From: Soren Stoutner via <help-guix@gnu.org>
To: help-guix@gnu.org
Subject: make check never finishes
Date: Wed, 17 May 2023 06:54:34 -0700 [thread overview]
Message-ID: <140363212.2u7i6HKcc6@soren-desktop> (raw)
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
I am new to GNU Guix. In my attempts to build Guix I run into a problem
where `make check` never finishes. The last check to complete is the
following:
PASS: tests/guix-pack-localstatedir.sh
I think the problem happens while processing guix-pack-relocatable.sh.
The final lines of guix-pack-relocatable.log are the following:
The following derivations will be built:
/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.
Does anyone have any ideas of what might be wrong?
--
Soren Stoutner
soren@stoutner.com
623-262-6169
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-05-17 15:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 13:54 Soren Stoutner via [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=140363212.2u7i6HKcc6@soren-desktop \
--to=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).