From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: bug-guix@gnu.org
Subject: Re: [PATCH] distro: Add Kmod.
Date: Wed, 19 Dec 2012 13:31:18 +0100 [thread overview]
Message-ID: <87r4mmdy09.fsf@gnu.org> (raw)
In-Reply-To: <87bodqoig1.fsf@karetnikov.org> (Nikita Karetnikov's message of "Tue, 18 Dec 2012 21:59:50 -0500")
Hi,
Nikita Karetnikov <nikita@karetnikov.org> skribis:
> Can we fix the following? Should we report it instead?
>
> TESTSUITE: ERR: sizes do not match /tmp/nix-build-p7bkz7iscax3f0998gss17sfm83k9v7q-kmod-12.drv-0/kmod-12/testsuite/rootfs/test-depmod/modules-order-compressed/lib/modules/3.5.4-1-ARCH/correct-modules.alias /tmp/nix-build-p7bkz7iscax3f0998gss17sfm83k9v7q-kmod-12.drv-0/kmod-12/testsuite/rootfs/test-depmod/modules-order-compressed/lib/modules/3.5.4-1-ARCH/modules.alias
> TESTSUITE: ERR: FAILED: exit ok but outputs do not match: depmod_modules_order_for_compressed
> FAIL: testsuite/test-depmod
> ==============================================
> 2 of 10 tests failed
> Please report to linux-modules@vger.kernel.org
> ==============================================
Can you look at the detailed build logs?
Often, when tests fail to build in our chroot, that’s because:
• they refer to absolute file names (/usr/bin/modprobe,
/lib/modules/xxx, etc.)
• they have scripts with shebangs pointing to a file missing in the
chroot (#!/usr/bin/env, #!/bin/bash, etc.)
• they attempt to do name lookups, which fails because the chroot
lacks /etc/resolv.conf, /etc/services, etc.
If that is the case, a phase must be inserted before the ‘check’ phase
to adjust the faulty files.
HTH,
Ludo’.
next prev parent reply other threads:[~2012-12-19 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 2:59 [PATCH] distro: Add Kmod Nikita Karetnikov
2012-12-19 12:31 ` Ludovic Courtès [this message]
2012-12-24 19:21 ` Nikita Karetnikov
2012-12-24 22:22 ` Nikita Karetnikov
2012-12-30 14:15 ` Ludovic Courtès
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=87r4mmdy09.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guix@gnu.org \
--cc=nikita@karetnikov.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).