Bug#973271: glib2.0 autopkgtest-virt-lxc failure as uid 0 on arm64

[Simon McVittie]

Control: retitle -1 glib2.0 autopkgtest-virt-lxc failure as uid 0 on arm64

On Wed, 28 Oct 2020 at 14:47:18 +0900, Ryutaroh Matsumoto wrote:
> autopkgtest-virt-lxc fails on arm64 as follows.
> (I used Raspberry Pi 4B running latest Debian testing).
> 
> GLib:ERROR:../../../glib/tests/fileutils.c:1150:test_set_contents_full_read_only_file: assertion failed (error == (g-file-error-quark, 2)): error is NULL
> Bail out! GLib:ERROR:../../../glib/tests/fileutils.c:1150:test_set_contents_full_read_only_file: assertion failed (error == (g-file-error-quark, 2)): error is NULL
> FAIL: glib/fileutils.test (Child process killed by signal 6)

>From the log:

> Running as: uid=0(root) gid=0(root) groups=0(root)
> passwd entry: root:x:0:0:root:/root:/bin/bash
> group entry: root:x:0:

I think this is probably failing because you're root, rather than because
you're running on amd64 or under autopkgtest-virt-lxc. This test doesn't
account for the fact that uid 0 normally has CAP_DAC_OVERRIDE and so
can override filesystem permissions. I'll look into fixing that.

When reporting test failures as bugs, please mention running all tests as
uid 0 as a non-standard aspect of your configuration. In principle it is
something that *should* work, but it's unusual: the normal configuration
for an autopkgtest runner (for example on ci.debian.net) is to run tests
that have "Restrictions: needs-root" as root, and all other tests as an
unprivileged user.

It's quite common for packages to have build-time tests or autopkgtests
that fail when run as root, either because the developer didn't expect
that anyone would do that, or because the developer actively refuses to
support it (for example tools that stop with an error message when run
as root to avoid disastrous mistakes).

    smcv