Question - testing writes to systemd journal in mock (for build in Koji) (re-sent)

[Robert Fairley]

(re-sending as previous email was in HTML text mode, please disregard previous
email if received)

Hello,

The `rust-libsystemd` [1] package runs some upstream tests as part of `%{check}`
which involve writing to `/run/systemd/journal/socket`. Running in a system
loaded with systemd, these tests pass. However, in a mock chroot in Koji (with
Rawhide target), these tests fail due to `/run/systemd/journal/socket` not
found, with full log at [2].

Is there currently a way to expose `systemd-journald` endpoints within the mock
chroot, or a common workaround for this type of issue (maybe manually create the
needed file within `%{check}` before running the tests)?

If not, excluding the tests for the RPM build would be sufficient as done in [3]
- the upstream tests can be verified locally whenever updating the package. Just
wanted to check if there is currently a way that wouldn't require excluding the
tests during the Koji build.

Thanks,

Robert Fairley

[1] https://src.fedoraproject.org/rpms/rust-libsystemd
[2] https://kojipkgs.fedoraproject.org//work/tasks/5632/43695632/build.log
[3] https://src.fedoraproject.org/rpms/rust-libsystemd/c/b8607817d63dc70aac5c25c...