Re: [PATCH] distro: Add Kmod.

[ludo@gnu.org (Ludovic Courtès)]

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’.