aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorOphestra <cat@gensokyo.uk>2025-04-15 20:45:31 +0900
committerOphestra <cat@gensokyo.uk>2025-04-15 20:45:31 +0900
commite587112e6382aae80d46097c2e7636e22abdf917 (patch)
tree77bbeb8a83d577bc5f9e1c6f37f6c58f0d05afb0
parentd6cf736abf3f7d34643af66fb8e62f071c2289f2 (diff)
test: check xdg-dbus-proxy termination
This process runs outside the application container's pid namespace, so it is a good idea to check whether its lifecycle becomes decoupled from the application. Signed-off-by: Ophestra <cat@gensokyo.uk>
-rw-r--r--test/test.py2
1 files changed, 2 insertions, 0 deletions
diff --git a/test/test.py b/test/test.py
index d72dafbd..ceb067e4 100644
--- a/test/test.py
+++ b/test/test.py
@@ -152,6 +152,8 @@ print(machine.fail("sudo -u alice -i fortify -v run --wayland true"))
fortify('-v run --wayland --dbus notify-send -a "NixOS Tests" "Test notification" "Notification from within sandbox." && touch /tmp/dbus-ok')
machine.wait_for_file("/tmp/dbus-ok", timeout=15)
collect_state_ui("dbus_notify_exited")
+# not in pid namespace, verify termination
+machine.wait_until_fails("pgrep xdg-dbus-proxy")
machine.succeed("pkill -9 mako")
# Check revert type selection: