From 738a47fd987c36395b93b56d01f125f7a1754692 Mon Sep 17 00:00:00 2001 From: Ivan Kruglov Date: Thu, 22 May 2025 07:05:10 -0700 Subject: [PATCH] tests: fix TEST-74-AUX-UTILS.varlinkctl.sh (#37562) per Daan's explanation: other subtests running as testuser apparently use systemd-run --user --machine testuser@.host which turns user tracking in logind into "by pin" mode. when the last pinning session exits it terminates the user. --- test/units/TEST-74-AUX-UTILS.varlinkctl.sh | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/test/units/TEST-74-AUX-UTILS.varlinkctl.sh b/test/units/TEST-74-AUX-UTILS.varlinkctl.sh index 07b857e47d..83f8ac3532 100755 --- a/test/units/TEST-74-AUX-UTILS.varlinkctl.sh +++ b/test/units/TEST-74-AUX-UTILS.varlinkctl.sh @@ -173,7 +173,10 @@ varlinkctl introspect /run/systemd/io.systemd.Manager io.systemd.Manager varlinkctl call /run/systemd/io.systemd.Manager io.systemd.Manager.Describe '{}' # test io.systemd.Manager in user manager -systemctl start user@4711 -varlinkctl info /run/user/4711/systemd/io.systemd.Manager -varlinkctl introspect /run/user/4711/systemd/io.systemd.Manager -varlinkctl call /run/user/4711/systemd/io.systemd.Manager io.systemd.Manager.Describe '{}' +testuser_uid=$(id -u testuser) +systemd-run --wait --pipe --user --machine testuser@ \ + varlinkctl info /run/user/"$testuser_uid"/systemd/io.systemd.Manager +systemd-run --wait --pipe --user --machine testuser@ \ + varlinkctl introspect /run/user/"$testuser_uid"/systemd/io.systemd.Manager +systemd-run --wait --pipe --user --machine testuser@ \ + varlinkctl call /run/user/"$testuser_uid"/systemd/io.systemd.Manager io.systemd.Manager.Describe '{}'