Package: udev Version: 215-5 Severity: minor This was an attempted clone from #767909 but that doesn't work as it's a merged bug. So filing as a new one.
Julien Cristau [2014-11-03 14:12 +0100]:
> your package no longer builds on the arm64 buildd:
> > ERROR:tests/test-umockdev-record.c:369:t_testbed_one: assertion failed
> > (serr == ""): ("calling: info\n" == "")
So this is really curious. I confirmed this on asachi.debian.org,
where calling udevadm info indeed spews "calling: info" on stderr:
(sid_armhf-dchroot)mpitt@asachi:~$ /sbin/udevadm info --query=all --name=sda
>/dev/null
calling: info
(udev 215-5). This doesn't happen on any other architecture, and it
doesn't happen on the asachi host either (udev 175-7.2), just in the
schroot.
I don't find anything which would explain the "calling: info" debug
message from udev:
src/udev/udevadm.c: log_debug("calling: %s", cmd->name);
The three ways of getting that debug message are:
- udevadm's -d/--debug option, but we don't supply that
- set udev_log in /etc/udev/udev.conf (but the conf file isn't
modified, and the key is commented out)
- set $UDEV_LOG env var (but it isn't set)
There are no other calls to udev_set_log_priority().
I tried libudev directly, without udevadm, and the problem doesn't
happen there:
python3 -c 'from gi.repository import GUdev; c = GUdev.Client();
print(c.query_by_subsystem("block"))'
This doesn't print out any debug messages, but calling it with
UDEV_LOG=debug does. So it seems this is a problem on armhf/arm64 with
udevadm in the first iteration?
I'll adjust umockdev to get along with debug messages, but I also
clone the bug to udev as showing debug messages by default certainly
isn't intended.
Thanks,
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
