[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] distro: Add Kmod.

From: Ludovic Courtès
Subject: Re: [PATCH] distro: Add Kmod.
Date: Wed, 19 Dec 2012 13:31:18 +0100
User-agent: Gnus/5.130005 (Ma Gnus v0.5) Emacs/24.2 (gnu/linux)


Nikita Karetnikov <address@hidden> 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 address@hidden
> ==============================================

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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]