From: Marius Bakke <mbakke@fastmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>, 41090-done@debbugs.gnu.org
Subject: bug#41090: [core-updates] fakeroot fails its test suite (breaks spacefm)
Date: Tue, 05 May 2020 16:36:54 +0200 [thread overview]
Message-ID: <87mu6mzbw9.fsf@devup.no> (raw)
In-Reply-To: <878si72qle.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1829 bytes --]
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> Hello,
>
> Testing the core-updates branch, I got this failure from fakeroot:
>
> --8<---------------cut here---------------start------------->8---
> make check-TESTS
> make[2]: Entering directory '/tmp/guix-build-fakeroot-1.24.drv-0/fakeroot-1.24/test'
> make[3]: Entering directory '/tmp/guix-build-fakeroot-1.24.drv-0/fakeroot-1.24/test'
> PASS: t.falsereturn
> PASS: t.truereturn
> PASS: t.option
> PASS: t.echoarg
> FAIL: t.mknod
> PASS: t.touchinstall
> FAIL: t.chmod_dev
> PASS: t.no_ld_preload
> PASS: t.no_ld_preload_link
> FAIL: t.xattr
> PASS: t.cp-a
> PASS: t.tar
> ========================================
> fakeroot 1.24: test/test-suite.log
> ========================================
>
> # TOTAL: 12
> # PASS: 9
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 3
> # XPASS: 0
> # ERROR: 0
>
> .. contents:: :depth: 2
>
> FAIL: t.chmod_dev
> =================
>
> -rw-r--r-- 1 nixbld nixbld 0 May 5 00:04 t.chmod_dev.dir/hda3
> FAIL t.chmod_dev (exit status: 1)
>
> FAIL: t.mknod
> =============
>
> -rw-r--r-- 1 nixbld nixbld 0 May 5 00:04 t.mknod.dir/hda3
> FAIL t.mknod (exit status: 1)
These two tests create a block device with 'mknod' inside the fakeroot,
and afterwards verifies with 'ls' that they are in fact block devices.
It turns out that the 'ls' invokation does not work because the newer
'ls' uses statx() which is not supported/caught by fakeroot, and thus it
does not see the fake block device. So I changed these tests to use
'test -b' as a stopgap measure.
> FAIL: t.xattr
> =============
>
> unable to set CAP_SETFCAP effective capability: Operation not permitted
> FAIL t.xattr (exit status: 1)
This turned out to be a regression in 'libcap', fixed by providing a
newer version.
Fixed in ba151b7e1a9cc0baf932b5c5e0c916e54d2e27f4, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2020-05-05 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 0:05 bug#41090: [core-updates] fakeroot fails its test suite (breaks spacefm) Maxim Cournoyer
2020-05-05 14:36 ` Marius Bakke [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mu6mzbw9.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=41090-done@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.