From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: 33106@debbugs.gnu.org
Subject: bug#33106: "make check-system TESTS=basic" fails on master
Date: Mon, 22 Oct 2018 15:11:54 +0200 [thread overview]
Message-ID: <87pnw2jfc5.fsf@gnu.org> (raw)
In-Reply-To: <87k1mcqvt5.fsf@gmail.com> (Chris Marusich's message of "Sat, 20 Oct 2018 12:09:42 -0700")
Hello,
Chris Marusich <cmmarusich@gmail.com> skribis:
> The system test "basic" fails on commit
> 7d1f21c69aa89e4c7c57ace26af80d168157b243 (master). To reproduce, check
> out that commit and run:
>
> make check-system TESTS="basic"
It passes for me as of ff598353c01b1953243ba0ecb87efbd73c66720e, on
x86_64-linux.
[...]
> [ 1.701890] virtio_blk: probe of virtio4 failed with error -2
> [ 1.718210] virtio_net: probe of virtio0 failed with error -2
> [ 1.724827] virtio_console virtio3: Error -2 initializing vqs
> [ 1.726493] virtio_console: probe of virtio3 failed with error -2
> [ 1.732626] virtio_rng: probe of virtio1 failed with error -2
> [ 1.747209] FS-Cache: Loaded
> [ 1.753755] 9pnet: Installing 9P2000 support
> [ 1.756817] 9p: Installing v9fs 9p2000 file system support
> [ 1.758476] FS-Cache: Netfs '9p' registered for caching
> [ 1.767544] 9pnet_virtio: probe of virtio2 failed with error -2
> In gnu/build/linux-boot.scm:
> 516:13 2 (_)
> 367:8 1 (mount-root-file-system "/dev/vda1" "ext4" # _)
> In unknown file:
> [ 1.798957] random: fast init done
> 0 (mount "/dev/vda1" "/real-root" "ext4" 1 #<undefined>)
> In procedure mount: No such file or directory
> [ 1.808236] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000
Instead of these ‘virtio’ error, I see this (excerpt):
--8<---------------cut here---------------start------------->8---
Welcome, this is GNU's early boot Guile.
Use '--repl' for an initrd REPL.
loading kernel modules...
[ 0.652780] usbcore: registered new interface driver usb-storage
[ 0.654790] usbcore: registered new interface driver uas
[ 0.660951] hidraw: raw HID events driver (C) Jiri Kosina
[ 0.661917] usbcore: registered new interface driver usbhid
[ 0.662504] usbhid: USB HID core driver
[ 0.668512] isci: Intel(R) C600 SAS Controller Driver - version 1.2.0
[ 0.687586] PCI Interrupt Link [LNKC] enabled at IRQ 11
[ 0.706161] PCI Interrupt Link [LNKD] enabled at IRQ 10
[ 0.724746] PCI Interrupt Link [LNKA] enabled at IRQ 10
[ 0.743427] PCI Interrupt Link [LNKB] enabled at IRQ 11
[ 0.765047] virtio_blk virtio4: [vda] 143360 512-byte logical blocks (73.4 MB/70.0 MiB)
[ 0.766293] vda: vda1 vda2
[ 0.782675] FS-Cache: Loaded
[ 0.784778] 9pnet: Installing 9P2000 support
[ 0.785387] random: fast init done
[ 0.786349] 9p: Installing v9fs 9p2000 file system support
[ 0.787101] FS-Cache: Netfs '9p' registered for caching
[ 0.788027] random: crng init done
[ 0.792200] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
loading '/gnu/store/vwyynlbmkrg1mr4d56n6x9vcnfw9hnw2-system/boot'...
--8<---------------cut here---------------end--------------->8---
I could be a QEMU or a kernel error. Does it still manifest with
today’s master?
> %%%% Starting test basic (Writing full log to "basic.log")
> /gnu/store/b1f0pn2zp33b0q06cp39yk9p1qasxzqi-basic-builder:1: FAIL uname
> /gnu/store/b1f0pn2zp33b0q06cp39yk9p1qasxzqi-basic-builder:1: FAIL shepherd socket ready
> /gnu/store/b1f0pn2zp33b0q06cp39yk9p1qasxzqi-basic-builder:1: FAIL shell and user commands
> /gnu/store/b1f0pn2zp33b0q06cp39yk9p1qasxzqi-basic-builder:1: FAIL special files
> /gnu/store/b1f0pn2zp33b0q06cp39yk9p1qasxzqi-basic-builder:1: FAIL accounts
> /gnu/store/b1f0pn2zp33b0q06cp39yk9p1qasxzqi-basic-builder:1: FAIL shepherd services
> /gnu/store/b1f0pn2zp33b0q06cp39yk9p1qasxzqi-basic-builder:1: FAIL homes
> /gnu/store/b1f0pn2zp33b0q06cp39yk9p1qasxzqi-basic-builder:1: FAIL skeletons in home directories
> /gnu/store/b1f0pn2zp33b0q06cp39yk9p1qasxzqi-basic-builder:1: FAIL permissions on /root
> /gnu/store/b1f0pn2zp33b0q06cp39yk9p1qasxzqi-basic-builder:1: FAIL no extra home directories
> /gnu/store/b1f0pn2zp33b0q06cp39yk9p1qasxzqi-basic-builder:1: FAIL login on tty1
> /gnu/store/b1f0pn2zp33b0q06cp39yk9p1qasxzqi-basic-builder:2: FAIL utmpx entry
> /gnu/store/b1f0pn2zp33b0q06cp39yk9p1qasxzqi-basic-builder:2: FAIL wtmp entry
> /gnu/store/b1f0pn2zp33b0q06cp39yk9p1qasxzqi-basic-builder:2: FAIL host name resolution
> /gnu/store/b1f0pn2zp33b0q06cp39yk9p1qasxzqi-basic-builder:2: FAIL locale
> /gnu/store/b1f0pn2zp33b0q06cp39yk9p1qasxzqi-basic-builder:2: FAIL /run/current-system is a GC root
> /gnu/store/b1f0pn2zp33b0q06cp39yk9p1qasxzqi-basic-builder:2: FAIL /var/guix/gcroots/profiles is a valid symlink
> /gnu/store/b1f0pn2zp33b0q06cp39yk9p1qasxzqi-basic-builder:2: FAIL screendump
> /gnu/store/b1f0pn2zp33b0q06cp39yk9p1qasxzqi-basic-builder:2: FAIL screen text
> # of expected passes 1
> # of unexpected failures 19
>
>
> Some questions/observations:
>
> 1) Where is the "basic.log" file? I checked the Guix checkout and the
> retained directory of the failed derivation (i.e., the directory
> produced by guix build --keep-failed /gnu/store/...gjmid5-basic.drv),
> but I don't see it anywhere.
The ‘basic.log’ file is in the output of this derivation. The
derivation is built with #:keep-failed? #t, so the output is still
around upon failure and ‘make check-system’ prints it upon completion
with something like:
TOTAL: 1
FAIL: /gnu/store/gmsv8dlxd88p37qc74pdn5jgiikbyxwv-basic
Thanks for your report,
Ludo’.
next prev parent reply other threads:[~2018-10-22 13:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 19:09 bug#33106: "make check-system TESTS=basic" fails on master Chris Marusich
2018-10-22 13:11 ` Ludovic Courtès [this message]
2018-10-23 8:58 ` Chris Marusich
2018-10-24 1:49 ` Chris Marusich
2018-10-24 12:14 ` Ludovic Courtès
2018-10-26 5:11 ` Chris Marusich
2018-10-26 9:44 ` Ludovic Courtès
2018-10-26 16:14 ` Chris Marusich
2018-10-27 14:37 ` Ludovic Courtès
2020-11-30 21:36 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-12-19 9:08 ` zimoun
2020-12-22 14:13 ` zimoun
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=87pnw2jfc5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33106@debbugs.gnu.org \
--cc=cmmarusich@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).