From: zimoun <zimon.toutoune@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: 30027@debbugs.gnu.org
Subject: bug#30027: core-updates: guile build hung during tests with defunct guile process
Date: Thu, 03 Dec 2020 01:05:18 +0100 [thread overview]
Message-ID: <86sg8nzrcx.fsf@gmail.com> (raw)
In-Reply-To: <87mv1oe2b7.fsf@netris.org> (Mark H. Weaver's message of "Mon, 08 Jan 2018 11:35:24 -0500")
Hi Mark,
This old bug #30027 is about core-updates and Guile (2.2).
<http://issues.guix.gnu.org/issue/30027>
On Mon, 08 Jan 2018 at 11:35, Mark H Weaver <mhw@netris.org> wrote:
> While building core-updates locally on my x86_64 system running GuixSD,
> my first attempt to build guile-2.2.3 got hung up during the test suite.
> There was no CPU usage or terminal output for over 30 minutes, and 'ps'
> showed a defunct guile process at the bottom of the process tree.
>
> My second attempt to build it succeeded. Note that this is not
> 'guile-final', but rather the same derivation that would be built by
> "guix build guile". Also note that I do not use binary substitutes, so
> everything is built locally.
>
> Here's the tail of the build log, followed by an excerpt of "ps auxwwf"
> output:
>
> starting phase `check'
> GEN public-submodule-commit
> make check-recursive
> make[1]: Entering directory '/tmp/guix-build-guile-2.2.3.drv-0/guile-2.2.3'
[...]
> mhw@jojen ~/guix-mhw-core-updates$ cat ~/GUIX_CORE_UPDATES_HUNG_GUILE_BUILD_PS
[...]
> guixbui+ 20862 0.0 0.0 0 0 ? Z 01:17 0:00 \_ [guile] <defunct>
Is it still relevant? Or can we close it?
All the best,
simon
next prev parent reply other threads:[~2020-12-03 0:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 16:35 bug#30027: core-updates: guile build hung during tests with defunct guile process Mark H Weaver
2020-12-03 0:05 ` zimoun [this message]
2020-12-03 3:27 ` Mark H Weaver
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86sg8nzrcx.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=30027@debbugs.gnu.org \
--cc=mhw@netris.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.