From: Danny Milosavljevic <dannym@scratchpost.org>
To: 43257@debbugs.gnu.org
Cc: guix-devel@gnu.org
Subject: Spooky problem in "nfs-root-os" system test
Date: Sun, 13 Sep 2020 21:52:14 +0200 [thread overview]
Message-ID: <20200913215214.7ff9b97f@scratchpost.org> (raw)
In-Reply-To: <20200910152042.4b33a84f@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
Hi,
I've got some spooky problem in the NFS root test (or in the VM setup by Guix,
really).
It seems to hang the system test in a part I cannot change (so it's not inside
the test script).
In order to reproduce, start with guix master commit
898fbb60b2354e82e5b7f259b44dbfed112a83aa--or any recent Guix master commit.
So far it's still "fine"-ish:
$ make TESTS="nfs-root-fs" check-system
[... works fine and eventually fails because port 20001 is waited for but is
never opened by the server--so far so good]
Now edit gnu/tests/nfs.scm to change
;(rpcmountd-port 20001)
to
(rpcmountd-port 20001)
in order to fix the problem above--or so I thought.
$ make TESTS="nfs-root-fs" check-system
[... hangs in first VM--without even trying to start up the NFS server VM (as
far as I can tell)]
What is going on? Also, how to debug this?
(same happens when enabling (rpcstatd-port 20002) only.
Also, doesn't rpcstatd have TWO ports--one to broadcast and one to listen?
How does one set up both using the operating-system configuration?)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-09-13 19:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 16:47 [bug#43257] [PATCH] services: nfs: Require file-systems to be mounted before starting NFS shepherd service Danny Milosavljevic
2020-09-09 8:27 ` Ludovic Courtès
2020-09-09 10:13 ` Danny Milosavljevic
2020-09-10 7:42 ` Ludovic Courtès
2020-09-10 13:20 ` Danny Milosavljevic
2020-09-11 7:02 ` Ludovic Courtès
2020-09-11 8:23 ` Danny Milosavljevic
2020-09-11 14:47 ` Ludovic Courtès
2020-09-11 17:50 ` Danny Milosavljevic
2020-09-13 19:52 ` Danny Milosavljevic [this message]
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=20200913215214.7ff9b97f@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=43257@debbugs.gnu.org \
--cc=guix-devel@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.
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.