From: ludo@gnu.org (Ludovic Courtès)
To: Guix-devel <Guix-devel@gnu.org>
Subject: util-linux test failure
Date: Tue, 19 Jan 2016 11:34:48 +0100 [thread overview]
Message-ID: <87ziw1c0xj.fsf_-_@gnu.org> (raw)
In-Reply-To: <87oacp2wxb.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 13 Jan 2016 18:48:00 +0100")
[-- Attachment #1: Type: text/plain, Size: 2519 bytes --]
Hi!
util-linux had two test failures on i686. From
<http://hydra.gnu.org/build/949334/nixlog/2/raw>:
--8<---------------cut here---------------start------------->8---
fdisk: invalid input tests ... FAILED (fdisk/oddinput)
[...]
misc: rev ... OK
misc: setarch ... FAILED (misc/setarch)
[...]
---------------------------------------------------------------------
2 tests of 170 FAILED
---------------------------------------------------------------------
Makefile:12013: recipe for target 'check-local-tests' failed
make[3]: *** [check-local-tests] Error 1
make[3]: Leaving directory '/tmp/guix-build-util-linux-2.27.drv-0/util-linux-2.27'
--8<---------------cut here---------------end--------------->8---
On my laptop, commit v0.9.0-1181-gafe9f40, I’ve successfully run:
./pre-inst-env guix build util-linux -K -s i686-linux --rounds=3
which leads:
/gnu/store/l1v12p64hv4373m1z7a16ar9s5cw1lwi-util-linux-2.27
SHA256: 18axyw2qhr7sq1jd15r6l02nkx9rijzws0xqlcl07d95v8xwbwj7
However, I’ve noticed that these tests consume quite few tens of MB in
disk images:
--8<---------------cut here---------------start------------->8---
./ts/libfdisk/gpt:27:TEST_IMAGE_NAME=$(ts_image_init 10)
./ts/fdisk/oddinput:28:TEST_IMAGE_NAME=$(ts_image_init 10)
./ts/fdisk/bsd:89:TEST_IMAGE_NAME=$(ts_image_init 10)
./ts/fdisk/gpt:44:TEST_IMAGE_NAME=$(ts_image_init 10)
./ts/fdisk/mbr-dos-mode:52:TEST_IMAGE_NAME=$(ts_image_init 10)
./ts/fdisk/mbr-nondos-mode:48:TEST_IMAGE_NAME=$(ts_image_init 20) # 20 MiB
./ts/fdisk/id:29:TEST_IMAGE_NAME=$(ts_image_init 10)
./ts/fdisk/mbr-sort:50:TEST_IMAGE_NAME=$(ts_image_init 20) # 20 MiB
./ts/fdisk/sunlabel:40:TEST_IMAGE_NAME=$(ts_image_init 10)
./ts/libmount/context-py:140:img=$(ts_image_init)
./ts/libmount/context:138:img=$(ts_image_init)
./ts/losetup/losetup:42:BACKFILE=$(ts_image_init 10)
./ts/mount/regfile:19:IMAGE=$(ts_image_init)
--8<---------------cut here---------------end--------------->8---
So the fdisk test failure above could well be due to that.
The ‘setarch’ failure is less clear. It could be due to an old kernel
that does not support this personality(2) call on the host machine.
I’ve restarted the build from hydra.gnu.org, where it was scheduled on
hydra.gnunet.org, and it passed this time (with the same content hash as
above.)
So we can keep building ‘core-updates’. :-)
Ludo’.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
prev parent reply other threads:[~2016-01-19 10:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-03 14:35 Freezing core-updates soon Ludovic Courtès
2016-01-03 16:25 ` Ricardo Wurmus
2016-01-03 22:27 ` Ludovic Courtès
2016-01-04 14:20 ` Mark H Weaver
2016-01-04 21:16 ` Mark H Weaver
2016-01-04 22:49 ` Ludovic Courtès
2016-01-04 0:59 ` Thompson, David
2016-01-04 1:17 ` Ben Woodcroft
2016-01-04 10:46 ` [PATCH] Update Ruby to 2.3.0 (was Re: Freezing core-updates soon) Ben Woodcroft
2016-01-05 22:24 ` Ludovic Courtès
2016-01-08 11:16 ` Ben Woodcroft
2016-01-08 16:52 ` [PATCH] Update Ruby to 2.3.0 Ludovic Courtès
2016-01-10 12:53 ` Ben Woodcroft
2016-01-10 12:56 ` Ben Woodcroft
2016-01-10 21:14 ` Ludovic Courtès
2016-01-11 12:52 ` Ben Woodcroft
2016-01-04 11:02 ` Freezing core-updates soon Efraim Flashner
2016-01-04 15:13 ` Ludovic Courtès
2016-01-04 15:21 ` Efraim Flashner
2016-01-13 17:48 ` Ludovic Courtès
2016-01-14 20:10 ` Mark H Weaver
2016-01-15 16:13 ` Ludovic Courtès
2016-01-19 10:34 ` Ludovic Courtès [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
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=87ziw1c0xj.fsf_-_@gnu.org \
--to=ludo@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 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).