Yikes. Good point. Probably should be a comment there as this is non-standard (or maybe there was one I didn't see).

My daily integration tests were yelling at me, and confirming that this fixes stuff again. Thanks! 👍

oh, sorry.

hm, systemctl list-jobs always exits with 1.
It breaks my tests.

My daily integration tests were yelling at me

@martinpitt , where can I find these tests?

I mean, I changed a systemctl, run sudo make check, cd test; sudo make check. All tests passed. It's bad.

@evverx : They are in http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/tests . They are downstream integration tests using the built packages, so running them in an upstream context is not entirely straightforward. One test that failled on this was http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/tests/unit-config , this should actually work reasonably well by just directly calling it in a VM.

@martinpitt , thanks. I'll debcheckout it.

running them in an upstream context is not entirely straightforward

oh, I know.