From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 35719@debbugs.gnu.org
Subject: bug#35719: iso-image-install fails
Date: Wed, 15 May 2019 12:23:58 +0200 [thread overview]
Message-ID: <87imucvww1.fsf@gnu.org> (raw)
In-Reply-To: <20190513203057.79b7e431@scratchpost.org> (Danny Milosavljevic's message of "Mon, 13 May 2019 20:30:57 +0200")
Hello Danny,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> /gnu/store/3c4y81fr7r6lk5d4fpx1cyqkl4x64kz5-iso-image-installer-builder:1: FAIL shell and user commands
>
> ;;; (services (udev term-tty1 console-font-tty1 term-tty2 term-tty6 console-font-tty6 console-font-tty2 console-font-tty5 console-font-tty4 user-processes syslogd file-system-/dev/pts term-tty4 root-file-system user-homes console-font-tty3 loopback file-system-/gnu/store nscd urandom-seed host-name marionette term-auto guix-daemon root file-system-/dev/shm file-systems user-file-systems term-tty5 term-tty3 virtual-terminal))
> /gnu/store/3c4y81fr7r6lk5d4fpx1cyqkl4x64kz5-iso-image-installer-builder:1: FAIL skeletons in home directories
> /gnu/store/3c4y81fr7r6lk5d4fpx1cyqkl4x64kz5-iso-image-installer-builder:2: FAIL getlogin on tty1
> # of expected passes 22
> # of unexpected failures 3
When that happens, you have to look at the .log file in the failed build
tree (we should probably fix that and display that file automatically
upon completion.)
The ‘getlogin’ test was racy, which
8b310793d2b7d3cf5b3a5301423640dcf68e2528 fixes.
For the other tests, I don’t know: they pass for me for
“iso-image-installer”, “encrypted-root-os”, and “btrfs-root-os”.
Could you try again and get the ‘basic.log’ file upon failure?
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-05-15 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 18:30 bug#35719: iso-image-install fails Danny Milosavljevic
2019-05-15 10:23 ` Ludovic Courtès [this message]
2021-12-14 17:53 ` Maxim Cournoyer
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=87imucvww1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=35719@debbugs.gnu.org \
--cc=dannym@scratchpost.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.