If I chroot into a Gentoo linux image, I mound the /proc, /dev abd /dev/pts from the host system onto the mounted loop device. However this let kmod-7 to fail most of the test cases. Is the "tes" - Use flag in this case wrong ? Reproducible: Always
Created attachment 305907 [details] build log
Well, even if I run the test withan a started user mode linuximage, I got failures: From upstream I got the question : >Did you configure it any different from what bootstrap-configure does? >We don't support random rootprefix, prefix, etc for running testsuite. >See testsuite/README, item #9. for the following mail: >>> I get with 3.2.12 as hsot system and 3.3 as guest : ... make --no-print-directory check-TESTS GEN testsuite/rootfs TESTSUITE: running test_initlib, in forked context TESTSUITE: 'test_initlib' [5644] exited with return code 0 TESTSUITE: PASSED: test_initlib TESTSUITE: running test_insert, in forked context TESTSUITE: ERR: could not insert module: No such file or directory TESTSUITE: ERR: 'test_insert' [5645] exited with return code 1 TESTSUITE: ERR: FAILED: test_insert FAIL: testsuite/test-init TESTSUITE: running testsuite_uname, in forked context TESTSUITE: 'testsuite_uname' [5651] exited with return code 0 TESTSUITE: PASSED: testsuite_uname TESTSUITE: running testsuite_rootfs_fopen, in forked context TESTSUITE: ERR: 'testsuite_rootfs_fopen' [5652] exited with return code 1 TESTSUITE: ERR: FAILED: testsuite_rootfs_fopen FAIL: testsuite/test-testsuite TESTSUITE: running loaded_1, in forked context libkmod: kmod_module_new_from_loaded: could not open /proc/modules: No such file or directory No such file or directory TESTSUITE: ERR: 'loaded_1' [5658] exited with return code 1 TESTSUITE: ERR: FAILED: loaded_1 FAIL: testsuite/test-loaded TESTSUITE: running modinfo_jonsmodules, in forked context ERROR: could not get modinfo from 'ext4_i686': No such file or directory ERROR: could not get modinfo from 'ext4_ppc64': No such file or directory ERROR: could not get modinfo from 'ext4_s390x': No such file or directory ERROR: could not get modinfo from 'ext4_x86_64': No such file or directory TESTSUITE: ERR: Outputs do not match on stdout: TESTSUITE: ERR: correct: filename: /ext4-i686.ko license: GPL description: Fourth Extended Filesystem author: Remy Card, Step TESTSUITE: ERR: wrong: filename: /ext4-i686.ko filename: /ext4-ppc64.ko filename: /ext4-s390x.ko filename: /ext4-x86_64.ko TESTSUITE: ERR: 'modinfo_jonsmodules' [5664] exited with return code 1 TESTSUITE: ERR: FAILED: modinfo_jonsmodules FAIL: testsuite/test-modinfo TESTSUITE: running alias_1, in forked context TESTSUITE: 'alias_1' [5670] exited with return code 0 TESTSUITE: PASSED: alias_1 PASS: testsuite/test-alias TESTSUITE: running from_name, in forked context TESTSUITE: 'from_name' [5674] exited with return code 0 TESTSUITE: PASSED: from_name TESTSUITE: running from_alias, in forked context TESTSUITE: 'from_alias' [5675] exited with return code 0 TESTSUITE: PASSED: from_alias PASS: testsuite/test-new-module TESTSUITE: running modprobe_show_depends, in forked context TESTSUITE: ERR: 'modprobe_show_depends' [5679] exited with return code 1 TESTSUITE: ERR: FAILED: modprobe_show_depends FAIL: testsuite/test-modprobe ============================================== 5 of 7 tests failed Please report to linux-modules@vger.kernel.org ============================================== make[2]: *** [check-TESTS] Error 1 make[1]: *** [check-am] Error 2 make: *** [check-recursive] Error 1 <<<
To answer upstream's question, yes we use a different prefix and rootprefix from the default. Another issue that he pointed out to me was that you would also need /sys. Without that there is no way to tell whether modules are loaded. He also pointed out, however, that the test suite is intended for kmod developers. Given this information, I have put a restriction in the kmod ebuild so that we will not attempt to run the test suite.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ccfb9e9f8433a844b3d2f2d9a1dd0c0d05e1f6df commit ccfb9e9f8433a844b3d2f2d9a1dd0c0d05e1f6df Author: Sam James <sam@gentoo.org> AuthorDate: 2023-02-03 19:00:18 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-02-03 19:03:22 +0000 sys-apps/kmod: enable py3.11 and add python bindings smoketest Thanks to Andrés for the suggestion for the Python test. Now we can add future Python implementations with confidence. Closes: https://bugs.gentoo.org/408915 Thanks-to: Andrés Becerra Sandoval <andres.becerra@gmail.com> Signed-off-by: Sam James <sam@gentoo.org> sys-apps/kmod/kmod-30-r1.ebuild | 23 +++++++++++++++++++++-- sys-apps/kmod/kmod-9999.ebuild | 25 ++++++++++++++++++++++--- 2 files changed, 43 insertions(+), 5 deletions(-)
Tagged the wrong bug, sorry
(In reply to Sam James from comment #5) > Tagged the wrong bug, sorry (was supposed to be bug 891975)
