test: drop polkit's service memory limits when running under sanitizers#611
Conversation
Since running under sanitizers is quite resource hungry. Follow-up for 7d9c06c.
systemd v258+ and later (since [0]) doesn't start a user manager instance for system users by default. This then means there's no user D-Bus instance for such user and some of our tests fail: + container_run_user testuser systemctl status --full --no-pager polkit.service + local user=testuser + shift + systemd-run -M testuser@polkit-container-14392 --user --wait --pipe systemctl status --full --no-pager polkit.service Failed to connect to system scope bus via local transport: No such file or directory Failed to start transient service unit: Transport endpoint is not connected ~# journalctl -M polkit-container-14392 -o short-monotonic --no-hostname -u systemd-logind --grep testuser [ 8259.764687] systemd-logind[180]: New session 'c15' of user 'testuser' with class 'background-light' and type 'unspecified'. To mitigate this, create a non-system user for the test (i.e. with UUID >= 1000), so we get the regular user/background instance instead of the light variants. [0] systemd/systemd@cf8f6cd
|
@jrybar-rh this should fix two out of three issues that the CI uncovered (and make it green again). For the third one I opened systemd/systemd#39714 - it doesn't break the CI per se, but it could hide potential issues, as the journal checks in the |
|
FTR: systemd/systemd#39714 has been fixed and the patch should get backported to v257 as well, so the coredump/sanitizer error collection should start working automagically again soon(-ish) |
2 participants
Since running under sanitizers is quite resource hungry.
Follow-up for 7d9c06c.