e3cccd3c2b
Let's parse the resolved JSON notifications via `jq` and check them in a bit more "controlled" manner - e.g. until now the `grep` was checking just a one gigantic JSON string, as all received notifications via the varlink socket are terminated by a NUL character, not a newline. Also, as the notification delivery is asynchronous, retry the check a couple of times if it fails (spotted in C8S jobs): ``` [ 2891.935879] testsuite-75.sh[36]: + : '--- nss-resolve/nss-myhostname tests' [ 2891.935988] testsuite-75.sh[36]: + run getent -s resolve hosts ns1.unsigned.test [ 2891.936542] testsuite-75.sh[177]: + getent -s resolve hosts ns1.unsigned.test [ 2891.937499] testsuite-75.sh[178]: + tee /tmp/tmp.pqjNvbQ2eS [ 2891.939977] testsuite-75.sh[178]: 10.0.0.1 ns1.unsigned.test [ 2891.940258] testsuite-75.sh[36]: + grep -qE '^10\.0\.0\.1\s+ns1\.unsigned\.test' /tmp/tmp.pqjNvbQ2eS [ 2891.942235] testsuite-75.sh[189]: + grep -qF '[10,0,0,1]' [ 2891.942577] testsuite-75.sh[188]: + grep -aF ns1.unsigned.test /tmp/notifications.txt [ 2891.943978] systemd[1]: testsuite-75.service: Child 36 belongs to testsuite-75.service. [ 2891.944112] systemd[1]: testsuite-75.service: Main process exited, code=exited, status=1/FAILURE [ 2891.944215] systemd[1]: testsuite-75.service: Failed with result 'exit-code'. ```
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.