From: Dmitry Matveyev <greenfork.lists@yandex.com>
To: help-guix@gnu.org
Subject: How to debug hanging "check" phase when building Kakoune
Date: Sun, 18 Apr 2021 12:26:20 +0600 [thread overview]
Message-ID: <87sg3ocdmb.fsf@yandex.com> (raw)
Hi,
I use guix on Arch Linux, version
050be36cbf3a42199f64f2e44c59f1cb1b3afab5.
When I run
guix build --check kakoune
everything builds correctly.
Now I change original `source` definition to fetch not from url but from
git repository. Original source and version:
(version "2020.09.01")
(source
(origin
(method url-fetch)
(uri (string-append "https://github.com/mawww/kakoune/"
"releases/download/v" version "/"
"kakoune-" version ".tar.bz2"))
(sha256
(base32 "0x81rxy7bqnhd9374g5ypy4w4nxmm0vnqw6b52bf62jxdg2qj6l6"))))
And my modified kakoune package:
(define-module (mykak)
#:use-module (guix packages)
#:use-module (guix git-download)
#:use-module (gnu packages text-editors))
(package
(inherit kakoune)
(version "2020.09.01")
(source
(origin
(method git-fetch)
(uri (git-reference
(url "https://github.com/mawww/kakoune.git")
(commit (string-append "v" version))))
(file-name (git-file-name "mykak" version))
(sha256
(base32
"091qzk0qs7hql0q51hix99srgma35mhdnjfd5ncfba1bmc1h8x5i")))))
Now when I run to build this package, assuming it is named
`kakoune.scm`:
guix build --check -f kakoune.scm
it freezes with this output:
phase `build' succeeded after 29.7 seconds
starting phase `check'
ln -sf kak.opt kak
cd ../test && ./run
kak-tests.R6Lc8cJk
compose
And the problem as I figured out with printf debugging is on this line:
https://github.com/mawww/kakoune/blob/v2020.09.01/test/run#L71
Same result is when I manually download tarball from github, unpack and
use it to build the package:
(define-module (mykak)
#:use-module (guix packages)
#:use-module (guix download)
#:use-module (guix gexp)
#:use-module (gnu packages text-editors))
(package
(inherit kakoune)
(version "2020.09.01")
(source
(local-file "/tmp/kakoune-2020.09.01" #:recursive? #t)))
I have assumption that this is somehow connected with read-write
permissions because when I keep failed builds and later try to delete
them, it asks whether I really want to delete some read-only files.
I have no idea how exactly that `test/run` script works with all the
pipes and output redirection. And I have no idea how to check why this
build phase hangs. Any tips would be really helpful.
Regards,
Dmitry.
next reply other threads:[~2021-04-18 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-18 6:26 Dmitry Matveyev [this message]
2021-04-18 10:42 ` How to debug hanging "check" phase when building Kakoune Ekaitz Zarraga
2021-04-18 14:12 ` Dmitry Matveyev
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=87sg3ocdmb.fsf@yandex.com \
--to=greenfork.lists@yandex.com \
--cc=help-guix@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).