On Fri, Sep 09, 2016 at 09:52:23AM +0300, Niko Tyni wrote: > Package: libgnome2-gconf-perl > Version: 1.044-6 > User: debian-p...@lists.debian.org > Usertags: autopkgtest > X-Debbugs-Cc: terce...@debian.org > > This package is failing its autopkgtest runs on ci.debian.net. > It broke between 2016-09-05 and 2016-09-08, probably related > to ci.debian.net updates > http://softwarelivre.org/terceiro/blog/debian-ci-updates-for-september-2016 > > adt-run [01:42:50]: test command1: /usr/share/pkg-perl-autopkgtest/runner > build-deps > adt-run [01:42:50]: test command1: [----------------------- > Failed to start message bus: Abstract socket name too long
> dbus-daemon --session --fork > --address="unix:abstract=$TDIR/dbus-libgnome2-gconf-perl" --print-pid=4 > 4>pid.tmp Some observations: - unix domain sockets have a maximum length of about 108 bytes - ci.debian.org apparently runs the tests under something like /tmp/tmp.t1UgJ2zs67/autopkgtest-incoming/unstable/amd64/libg/libgnome2-gconf-perl/20160917_041530 which is 98 bytes - abstract sockets don't have files associated to them, so the name doesn't really need to be "under" $TDIR - the name probably doesn't need to be unpredictable (the current one isn't really), although it might be nice as abstract sockets don't apparently have any permission controls (see unix(7)) - it would probably be nice for the name to be unique to the autopkgtest session so that concurrent sessions wouldn't clash - the current way of passing the socket name in smoke-env doesn't give much chance of executing commands to derive it (backticks might work, but that would be sort of abusing the interface IMO) I haven't been able to figure out a good solution yet. The best I came up with is to use something like 'autopkgtest-dbus-libgnome2-gconf-perl' and give up on the uniqueness constraint. Ideas welcome. -- Niko Tyni nt...@debian.org
