Hi Ludovic, Ludovic Courtès writes: > Hi Maxim, > > Maxim Cournoyer skribis: > >> Ludovic Courtès writes: > > [...] > >>> Before going further, I’d like to understand: this does more than just >>> fix the Jami system tests, right? >>> >>> It would have been nice to have surgical changes to “just” fix the >>> tests, along the lines of , >>> possibly followed by a rework of the whole machinery, if that’s >>> possible. >> >> It's not really possible unfortunately, because the rework from talking >> to the D-Bus API via the 'dbus-send' binary to using Guile AC/D-bus was >> needed or at least simplified fixing the issues. > > So am I right that the “issues” were not specifically related to the > Shepherd 0.9.0 switch, or at least not just to that? (Just to make sure > I understand the context.) I tried capturing the issue in the commit message, but I'll provide another more hands-on view: the Jami service was broken due to changes in Shepherd 0.9.0 that caused the blocking sleeps + concurrent make+forkexec-constructor/container and fork+exec-command combination used to not work anymore. This problem can be manually observed by spawning a VM with the Jami service: $(guix system vm --no-graphic -e '(@@ (gnu tests telephony) %jami-os)') -m 512 Then you'll see the service doesn't even start: --8<---------------cut here---------------start------------->8--- root@jami ~# herd status [...] Stopped: - jami [...] root@jami ~# pgrep jamid 192 root@jami ~# killall jamid root@jami ~# herd start jami Jami Daemon 11.0.0, by Savoir-faire Linux 2004-2019 https://jami.net/ [Video support enabled] [Plugins support enabled] 12:53:47.144 os_core_unix.c !pjlib 2.11 for POSIX initialized herd: exception caught while executing 'start' on service 'jami': Throw to key `match-error' with args `("match" "no matching pattern" #f)'. --8<---------------cut here---------------end--------------->8--- I've ran this: herd start jami& strace -p1 -f -s800 -o strace.out Attached is the last 10% of the gzip'd file. I couldn't explain this failure very clearly, but when I tried investigating it was failing on the '(dbus-service-available? "cx.ring.Ring")' call, if I recall correctly.