0s autopkgtest [03:29:02]: starting date and time: 2025-05-02 03:29:02+0000
0s autopkgtest [03:29:02]: git checkout: 9986aa8c Merge branch 'skia/fix_network_interface' into 'ubuntu/production'
0s autopkgtest [03:29:02]: host juju-7f2275-prod-proposed-migration-environment-21; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.zjqyq_86/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:guile-fibers --apt-upgrade shepherd --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=guile-fibers/1.3.1-5 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-cpu2-ram4-disk20-arm64 --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-21@sto01-arm64-8.secgroup --name adt-questing-arm64-shepherd-20250502-032902-juju-7f2275-prod-proposed-migration-environment-21-4e8d2cb7-1dfb-471e-989f-202aae596101 --image adt/ubuntu-questing-arm64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-21 --net-id=net_prod-autopkgtest-workers-arm64 -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/
104s autopkgtest [03:30:46]: testbed dpkg architecture: arm64
104s autopkgtest [03:30:46]: testbed apt version: 3.0.0
104s autopkgtest [03:30:46]: @@@@@@@@@@@@@@@@@@@@ test bed setup
104s autopkgtest [03:30:46]: testbed release detected to be: None
105s autopkgtest [03:30:47]: updating testbed package index (apt update)
105s Get:1 http://ftpmaster.internal/ubuntu questing-proposed InRelease [110 kB]
105s Hit:2 http://ftpmaster.internal/ubuntu questing InRelease
105s Hit:3 http://ftpmaster.internal/ubuntu questing-updates InRelease
105s Hit:4 http://ftpmaster.internal/ubuntu questing-security InRelease
105s Get:5 http://ftpmaster.internal/ubuntu questing-proposed/main Sources [190 kB]
105s Get:6 http://ftpmaster.internal/ubuntu questing-proposed/multiverse Sources [57.4 kB]
105s Get:7 http://ftpmaster.internal/ubuntu questing-proposed/universe Sources [2281 kB]
107s Get:8 http://ftpmaster.internal/ubuntu questing-proposed/main arm64 Packages [227 kB]
108s Get:9 http://ftpmaster.internal/ubuntu questing-proposed/universe arm64 Packages [1341 kB]
109s Get:10 http://ftpmaster.internal/ubuntu questing-proposed/multiverse arm64 Packages [16.5 kB]
109s Fetched 4223 kB in 4s (1044 kB/s)
110s Reading package lists...
110s autopkgtest [03:30:52]: upgrading testbed (apt dist-upgrade and autopurge)
111s Reading package lists...
111s Building dependency tree...
111s Reading state information...
111s Calculating upgrade...Starting pkgProblemResolver with broken count: 0
112s Starting 2 pkgProblemResolver with broken count: 0
112s Done
112s Entering ResolveByKeep
113s
113s Calculating upgrade...
113s The following packages will be upgraded:
113s libperl5.40 perl perl-base perl-modules-5.40
113s 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
113s Need to get 10.0 MB of archives.
113s After this operation, 0 B of additional disk space will be used.
113s Get:1 http://ftpmaster.internal/ubuntu questing-proposed/main arm64 libperl5.40 arm64 5.40.1-3 [4780 kB]
118s Get:2 http://ftpmaster.internal/ubuntu questing-proposed/main arm64 perl arm64 5.40.1-3 [262 kB]
118s Get:3 http://ftpmaster.internal/ubuntu questing-proposed/main arm64 perl-base arm64 5.40.1-3 [1786 kB]
119s Get:4 http://ftpmaster.internal/ubuntu questing-proposed/main arm64 perl-modules-5.40 all 5.40.1-3 [3217 kB]
123s Fetched 10.0 MB in 9s (1058 kB/s)
123s (Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 85224 files and directories currently installed.)
123s Preparing to unpack .../libperl5.40_5.40.1-3_arm64.deb ...
123s Unpacking libperl5.40:arm64 (5.40.1-3) over (5.40.1-2ubuntu0.1) ...
124s Preparing to unpack .../perl_5.40.1-3_arm64.deb ...
124s Unpacking perl (5.40.1-3) over (5.40.1-2ubuntu0.1) ...
124s Preparing to unpack .../perl-base_5.40.1-3_arm64.deb ...
124s Unpacking perl-base (5.40.1-3) over (5.40.1-2ubuntu0.1) ...
124s Setting up perl-base (5.40.1-3) ...
124s (Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 85224 files and directories currently installed.)
124s Preparing to unpack .../perl-modules-5.40_5.40.1-3_all.deb ...
124s Unpacking perl-modules-5.40 (5.40.1-3) over (5.40.1-2ubuntu0.1) ...
124s Setting up perl-modules-5.40 (5.40.1-3) ...
124s Setting up libperl5.40:arm64 (5.40.1-3) ...
124s Setting up perl (5.40.1-3) ...
124s Processing triggers for man-db (2.13.0-1) ...
125s Processing triggers for libc-bin (2.41-6ubuntu1) ...
125s Reading package lists...
125s Building dependency tree...
125s Reading state information...
126s Starting pkgProblemResolver with broken count: 0
126s Starting 2 pkgProblemResolver with broken count: 0
126s Done
126s Solving dependencies...
126s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
129s autopkgtest [03:31:11]: testbed running kernel: Linux 6.14.0-15-generic #15-Ubuntu SMP PREEMPT_DYNAMIC Sun Apr 6 14:37:51 UTC 2025
129s autopkgtest [03:31:11]: @@@@@@@@@@@@@@@@@@@@ apt-source shepherd
131s Get:1 http://ftpmaster.internal/ubuntu questing/universe shepherd 1.0.2-4 (dsc) [2568 B]
131s Get:2 http://ftpmaster.internal/ubuntu questing/universe shepherd 1.0.2-4 (tar) [811 kB]
131s Get:3 http://ftpmaster.internal/ubuntu questing/universe shepherd 1.0.2-4 (asc) [833 B]
131s Get:4 http://ftpmaster.internal/ubuntu questing/universe shepherd 1.0.2-4 (diff) [8432 B]
131s gpgv: Signature made Tue Mar 4 17:03:10 2025 UTC
131s gpgv: using EDDSA key A3CC9C870B9D310ABAD4CF2F51722B08FE4745A2
131s gpgv: issuer "simon@josefsson.org"
131s gpgv: Can't check signature: No public key
131s dpkg-source: warning: cannot verify inline signature for ./shepherd_1.0.2-4.dsc: no acceptable signature found
131s autopkgtest [03:31:13]: testing package shepherd version 1.0.2-4
132s autopkgtest [03:31:14]: build not needed
132s autopkgtest [03:31:14]: test herd--help: preparing testbed
132s Reading package lists...
133s Building dependency tree...
133s Reading state information...
133s Starting pkgProblemResolver with broken count: 0
133s Starting 2 pkgProblemResolver with broken count: 0
133s Done
134s The following NEW packages will be installed:
134s guile-3.0 guile-3.0-libs guile-fibers libgc1 shepherd
134s 0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
134s Need to get 9091 kB of archives.
134s After this operation, 64.6 MB of additional disk space will be used.
134s Get:1 http://ftpmaster.internal/ubuntu questing/main arm64 libgc1 arm64 1:8.2.8-1 [90.1 kB]
134s Get:2 http://ftpmaster.internal/ubuntu questing/universe arm64 guile-3.0-libs arm64 3.0.10+really3.0.10-4 [7891 kB]
141s Get:3 http://ftpmaster.internal/ubuntu questing/universe arm64 guile-3.0 arm64 3.0.10+really3.0.10-4 [16.4 kB]
141s Get:4 http://ftpmaster.internal/ubuntu questing-proposed/universe arm64 guile-fibers arm64 1.3.1-5 [332 kB]
142s Get:5 http://ftpmaster.internal/ubuntu questing/universe arm64 shepherd arm64 1.0.2-4 [763 kB]
143s Fetched 9091 kB in 9s (1038 kB/s)
143s Selecting previously unselected package libgc1:arm64.
143s (Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 85224 files and directories currently installed.)
143s Preparing to unpack .../libgc1_1%3a8.2.8-1_arm64.deb ...
143s Unpacking libgc1:arm64 (1:8.2.8-1) ...
143s Selecting previously unselected package guile-3.0-libs:arm64.
143s Preparing to unpack .../guile-3.0-libs_3.0.10+really3.0.10-4_arm64.deb ...
143s Unpacking guile-3.0-libs:arm64 (3.0.10+really3.0.10-4) ...
143s Selecting previously unselected package guile-3.0.
143s Preparing to unpack .../guile-3.0_3.0.10+really3.0.10-4_arm64.deb ...
143s Unpacking guile-3.0 (3.0.10+really3.0.10-4) ...
143s Selecting previously unselected package guile-fibers.
143s Preparing to unpack .../guile-fibers_1.3.1-5_arm64.deb ...
143s Unpacking guile-fibers (1.3.1-5) ...
143s Selecting previously unselected package shepherd.
143s Preparing to unpack .../shepherd_1.0.2-4_arm64.deb ...
143s Unpacking shepherd (1.0.2-4) ...
144s Setting up libgc1:arm64 (1:8.2.8-1) ...
144s Setting up guile-3.0-libs:arm64 (3.0.10+really3.0.10-4) ...
144s Setting up guile-3.0 (3.0.10+really3.0.10-4) ...
144s update-alternatives: using /usr/lib/aarch64-linux-gnu/guile/3.0/bin/guile to provide /usr/bin/guile (guile) in auto mode
144s Setting up guile-fibers (1.3.1-5) ...
144s Setting up shepherd (1.0.2-4) ...
144s Processing triggers for install-info (7.1.1-1) ...
144s Processing triggers for libc-bin (2.41-6ubuntu1) ...
144s Processing triggers for man-db (2.13.0-1) ...
145s autopkgtest [03:31:27]: test herd--help: herd --help
145s autopkgtest [03:31:27]: test herd--help: [-----------------------
145s herd [OPTIONS...] ACTION SERVICE [ARG...]
145s Apply ACTION (start, stop, status, etc.) on SERVICE with the ARGs.
145s --group=GROUP run the given program as GROUP
145s --user=USER run the given program as USER
145s -E, --environment-variable=ENVIRONMENT
145s pass the environment variable specified by ENVIRONMENT
145s -d, --working-directory=DIRECTORY
145s run service from DIRECTORY (for transient services)
145s --log-file=FILE log service output to FILE
145s -N, --service-name=NAME register new service under NAME
145s -n, --log-history=NUMBER display up to NUMBER service log lines
145s -s, --socket=FILE send commands to FILE
145s --help display this help and exit
145s --usage display short usage message and exit
145s --version display version information and exit
145s
145s Mandatory or optional arguments to long options are also mandatory or
145s optional to the corresponding short options.
145s
145s Report bugs to: bug-guix@gnu.org .
145s GNU Shepherd general home page:
145s General help using GNU software:
145s autopkgtest [03:31:27]: test herd--help: -----------------------]
146s herd--help PASS
146s autopkgtest [03:31:28]: test herd--help: - - - - - - - - - - results - - - - - - - - - -
146s autopkgtest [03:31:28]: test shepherd--help: preparing testbed
146s Reading package lists...
146s Building dependency tree...
146s Reading state information...
147s Starting pkgProblemResolver with broken count: 0
147s Starting 2 pkgProblemResolver with broken count: 0
147s Done
148s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
148s autopkgtest [03:31:30]: test shepherd--help: shepherd --help
148s autopkgtest [03:31:30]: test shepherd--help: [-----------------------
149s shepherd [OPTIONS...]
149s This is a service manager for Unix and GNU.
149s -s, --socket=FILE get commands from socket FILE or from stdin (-)
149s -c, --config=FILE read configuration from FILE
149s --pid[=FILE] when ready, write PID to FILE or stdout
149s -l, --logfile=FILE log actions in FILE
149s -I, --insecure don't ensure that the setup is secure
149s -S, --silent don't do output to stdout
149s --quiet synonym for --silent
149s --help display this help and exit
149s --usage display short usage message and exit
149s --version display version information and exit
149s
149s Mandatory or optional arguments to long options are also mandatory or
149s optional to the corresponding short options.
149s
149s Report bugs to: bug-guix@gnu.org .
149s GNU Shepherd general home page:
149s General help using GNU software:
149s autopkgtest [03:31:31]: test shepherd--help: -----------------------]
149s autopkgtest [03:31:31]: test shepherd--help: - - - - - - - - - - results - - - - - - - - - -
149s shepherd--help PASS
150s autopkgtest [03:31:32]: test herd--version: preparing testbed
150s Reading package lists...
150s Building dependency tree...
150s Reading state information...
150s Starting pkgProblemResolver with broken count: 0
150s Starting 2 pkgProblemResolver with broken count: 0
150s Done
151s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
152s autopkgtest [03:31:34]: test herd--version: herd --version
152s autopkgtest [03:31:34]: test herd--version: [-----------------------
152s herd (GNU Shepherd) 1.0.2
152s Copyright (C) 2025 the Shepherd authors
152s License GPLv3+: GNU GPL version 3 or later
152s This is free software: you are free to change and redistribute it.
152s There is NO WARRANTY, to the extent permitted by law.
152s autopkgtest [03:31:34]: test herd--version: -----------------------]
153s autopkgtest [03:31:35]: test herd--version: - - - - - - - - - - results - - - - - - - - - -
153s herd--version PASS
153s autopkgtest [03:31:35]: test shepherd--version: preparing testbed
153s Reading package lists...
153s Building dependency tree...
153s Reading state information...
154s Starting pkgProblemResolver with broken count: 0
154s Starting 2 pkgProblemResolver with broken count: 0
154s Done
154s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
155s autopkgtest [03:31:37]: test shepherd--version: shepherd --version
155s autopkgtest [03:31:37]: test shepherd--version: [-----------------------
155s shepherd (GNU Shepherd) 1.0.2
155s Copyright (C) 2025 the Shepherd authors
155s License GPLv3+: GNU GPL version 3 or later
155s This is free software: you are free to change and redistribute it.
155s There is NO WARRANTY, to the extent permitted by law.
156s autopkgtest [03:31:38]: test shepherd--version: -----------------------]
156s autopkgtest [03:31:38]: test shepherd--version: - - - - - - - - - - results - - - - - - - - - -
156s shepherd--version PASS
156s autopkgtest [03:31:38]: test tests-basic: preparing testbed
156s Reading package lists...
157s Building dependency tree...
157s Reading state information...
157s Starting pkgProblemResolver with broken count: 0
157s Starting 2 pkgProblemResolver with broken count: 0
157s Done
158s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
158s autopkgtest [03:31:40]: test tests-basic: sh -x tests/basic.sh
158s autopkgtest [03:31:40]: test tests-basic: [-----------------------
159s + shepherd --version
159s shepherd (GNU Shepherd) 1.0.2
159s Copyright (C) 2025 the Shepherd authors
159s License GPLv3+: GNU GPL version 3 or later
159s This is free software: you are free to change and redistribute it.
159s There is NO WARRANTY, to the extent permitted by law.
159s + herd --version
159s herd (GNU Shepherd) 1.0.2
159s Copyright (C) 2025 the Shepherd authors
159s License GPLv3+: GNU GPL version 3 or later
159s This is free software: you are free to change and redistribute it.
159s There is NO WARRANTY, to the extent permitted by law.
159s + socket=t-socket-2611
159s + conf=t-conf-2611
159s + confdir=t-confdir-2611
159s + datadir=t-datadir-2611
159s + log=t-log-2611
159s + stamp=t-stamp-2611
159s + pid=t-pid-2611
159s + herd=herd -s t-socket-2611
159s + trap cat t-log-2611 || true; rm -f t-socket-2611 t-conf-2611 t-stamp-2611 t-log-2611;
159s test -f t-pid-2611 && kill `cat t-pid-2611` || true; rm -f t-pid-2611 EXIT
159s + cat
159s + rm -f t-pid-2611
159s + test -f t-pid-2611
159s + sleep 0.3
159s + shepherd -I -s t-socket-2611 -c t-conf-2611 -l t-log-2611 --pid=t-pid-2611
159s GNU Shepherd 1.0.2 (Guile 3.0.10, aarch64-unknown-linux-gnu)
159s Starting service root...
159s Service root started.
159s Service root running with value #< id: 2622 command: #f>.
159s Service root has been started.
159s Configuration successfully loaded from 't-conf-2611'.
159s + test -f t-pid-2611
159s + cat t-pid-2611
159s + shepherd_pid=2622
159s + kill -0 2622
159s + test -S t-socket-2611
159s + herd -s t-socket-2611 status -n 0
159s + pristine_status=Started:
159s + root
159s Stopped:
159s - broken
159s - spawn-with-system
159s - test
159s - test-2
159s + echo Started: + root Stopped: - broken - spawn-with-system - test - test-2
159s + grep -E (Start.*root|Stop.*test)
159s Started: + root Stopped: - broken - spawn-with-system - test - test-2
159s + herd -s t-socket-2611 status root
159s + cat t-pid-2611
159s + grep PID: 2622
159s Main PID: 2622
159s + + grep Service root started
159s herd -s t-socket-2611 status root
159s 2025-05-02 03:31:41 Service root started.
159s + herd+ grep actions: .*eval
159s -s t-socket-2611 status root
159s Custom actions: help status halt power-off kexec load eval unload reload daemonize restart
159s + herd -s t-socket-2611 status root
159s + grep actions: .*load
159s + herd -s t-socket-2611 status root
159s + grep actions: .*halt
159s Custom actions: help status halt power-off kexec load eval unload reload daemonize restart
159s Custom actions: help status halt power-off kexec load eval unload reload daemonize restart
159s + herd -s t-socket-2611 graph
159s + grep "test-2" -> "test"
159s "test-2" -> "test";
159s + herd -s t-socket-2611 start test
159s Service test has been started.
159s + test -f t-stamp-2611
159s + herd -s t-socket-2611 status test
159s + grep running
159s It is running since 03:31:42 (0 seconds ago).
159s + herd -s t-socket-2611 status root
159s + grep Service test started
160s 2025-05-02 03:31:42 Service test started.
160s + herd -s t-socket-2611 stop test
160s + test -f t-stamp-2611
160s + herd -s t-socket-2611 log
160s 2 May 2025 03:31:41 service root is being started
160s 2 May 2025 03:31:41 service root is running
160s 2 May 2025 03:31:42 service test is being started
160s 2 May 2025 03:31:42 service test is running
160s 2 May 2025 03:31:42 service test is being stopped
160s 2 May 2025 03:31:42 service test is stopped
160s + herd -s t-socket-2611 log
160s + grep service test is running
160s 2 May 2025 03:31:42 service test is running
160s + herd -s t-socket-2611 log
160s + grep service test is stopped
160s 2 May 2025 03:31:42 service test is stopped
160s + herd -s t-socket-2611 status test
160s + grep stopped
160s It is stopped since 03:31:42 (0 seconds ago).
160s + herd -s t-socket-2611 stop test
160s + herd -s t-socket-2611 stop test
160s + test -z
160s + herd -s t-socket-2611 disable test-2
160s Disabled service test-2.
160s + herd -s t-socket-2611 start test-2
160s herd: error: failed to start service test-2
160s Service test has been started.
160s Service test-2 is currently disabled.
160s + true
160s + herd -s t-socket-2611 start test-2
160s + grep test-2 is currently disabled
160s herd: error: failed to start service test-2
160s Service test-2 is currently disabled.
160s + herd -s t-socket-2611 enable test-2
160s Enabled service test-2.
160s + herd -s t-socket-2611 start test-2
160s Service test-2 has been started.
160s + wc -l
160s + test 25 -gt 0
160s + cut -c+ grep ^$
160s 21-
160s + wc -l
160s + test 0 -eq 0
160s + herd -s t-socket-2611 doc test-2 action hi
160s + grep Say hi\.
160s hi: Say hi.
160s + herd -s t-socket-2611 hi test-2
160s start
160s
160s end
160s + herd -s t-socket-2611 hi test-2
160s + grep ^start$
160s start
160s + + grep ^end$
160s herd -s t-socket-2611 hi test-2
160s end
160s + herd -s t-socket-2611 hi test-2
160s + wc -l
160s + test 3 -eq 3
160s + herd -s t-socket-2611 fail test-2
160s + true
160s + herd -s t-socket-2611 enable test-2 with extra arguments
160s herd: error: exception caught while executing 'enable' on service 'test-2':
160s Wrong number of arguments to #
160s + true
160s + herd -s t-socket-2611 status test-2+
160s grep running
160s It is running since 03:31:42 (1 second ago).
160s + herd -s t-socket-2611 status test-2 something else that is useless
160s herd: error: exception caught while executing 'status' on service 'test-2':
160s Wrong number of arguments to #
160s + true
160s + herd -s t-socket-2611 status does-not-exist
160s herd: error: service 'does-not-exist' could not be found
160s + true
160s + + grep does-not-exist.*not.*found
160s herd -s t-socket-2611 status does-not-exist
160s herd: error: service 'does-not-exist' could not be found
160s + herd -s t-socket-2611 start does-not-exist
160s herd: error: service 'does-not-exist' could not be found
160s + true
160s + herd -s t-socket-2611 start does-not-exist
160s + grep does-not-exist.*not.*found
160s herd: error: service 'does-not-exist' could not be found
160s + herd -s t-socket-2611 stop does-not-exist
160s herd: error: service 'does-not-exist' could not be found
160s + true
160s + herd -s t-socket-2611 stop does-not-exist
160s + grep does-not-exist.*not.*found
160s herd: error: service 'does-not-exist' could not be found
160s + herd -s t-socket-2611 an-action-that-does-not-exist root
160s herd: error: service 'root' does not have an action 'an-action-that-does-not-exist'
160s herd: hint: Run 'herd doc root list-actions' to list supported actions.
160s + true
160s + herd -s t-socket-2611 start broken
160s herd: error: exception caught while executing 'start' on service 'broken':
160s In procedure mkdir: No such file or directory
160s + herd -s t-socket-2611 status broken
160s + grep stopped
160s It is stopped (failing).
160s + herd -s t-socket-2611 start spawn-with-system
160s Service spawn-with-system has been started.
160s + herd -s t-socket-2611 status spawn-with-system
160s + grep running
161s It is running since 03:31:43 (0 seconds ago).
161s + + grep starting from
161s herd -s t-socket-2611 status spawn-with-system
161s 2025-05-02 03:31:43 starting from /tmp/autopkgtest.482nKi/build.ox0/src
161s + herd -s t-socket-2611 stop spawn-with-system
161s + herd -s t-socket-2611 status spawn-with-system
161s + grep stopped
161s It is stopped since 03:31:43 (0 seconds ago).
161s + herd -s t-socket-2611 status root foo bar baz
161s herd: error: exception caught while executing 'status' on service 'root':
161s Wrong number of arguments to #
161s + true
161s + herd -s t-socket-2611 doc root action status
161s status: Return an s-expression showing information about all the services.
161s Clients such as 'herd' can read it and format it in a human-readable way.
161s + herd -s t-socket-2611 doc root action an-action-that-does-not-exist
161s herd: error: service 'root' does not have an action 'an-action-that-does-not-exist'
161s herd: hint: Run 'herd doc root list-actions' to list supported actions.
161s + true
161s + herd -s t-socket-2611 doc root action an-action-that-does-not-exist
161s + grep does not have an action 'an-action-that-does-not-exist'
161s herd: error: service 'root' does not have an action 'an-action-that-does-not-exist'
161s + herd -s t-socket-2611 doc root list-actions
161s + grep ^daemonize:
161s daemonize:
161s + herd -s t-socket-2611 doc root list-actions
161s + grep ^halt:
161s halt:
161s + herd -s t-socket-2611 load root /does/not/exist.scm
161s Loading /does/not/exist.scm.
161s herd: error: exception caught while executing 'load' on service 'root':
161s In procedure open-fdes: No such file or directory
161s + true
161s + herd -s t-socket-2611 unload root broken
161s Removing service 'broken'...
161s Service broken is not running.
161s Done.
161s + herd -s t-socket-2611 unload root test
161s Removing service 'test'...
161s Done.
161s + herd -s t-socket-2611 status -n 0
161s + grep -e - test-2
161s - test-2
161s + herd -s t-socket-2611 reload root t-conf-2611
161s Service test-2 is not running.
161s Service spawn-with-system is not running.
161s Loading t-conf-2611.
161s + herd -s t-socket-2611 status -n 0
161s + test Started:
161s + root
161s Stopped:
161s - broken
161s - spawn-with-system
161s - test
161s - test-2 == Started:
161s + root
161s Stopped:
161s - broken
161s - spawn-with-system
161s - test
161s - test-2
161s tests/basic.sh: 205: test: Started:
161s + root
161s Stopped:
161s - broken
161s - spawn-with-system
161s - test
161s - test-2: unexpected operator
161s + mkdir -p t-confdir-2611
161s + cat
161s + herd -s t-socket-2611 status test-loaded
161s herd: error: service 'test-loaded' could not be found
161s + true
161s + herd -s t-socket-2611 load root t-confdir-2611/some-conf.scm
161s + rm t-confdir-2611/some-conf.scm
161s + grep register-services.*rest list.*deprecated t-log-2611
161s Loading t-confdir-2611/some-conf.scm.
161s 2025-05-02 03:31:43 Passing 'register-services' services as a rest list is now deprecated.
161s + herd -s t-socket-2611 status test-loaded
161s ● Status of test-loaded:
161s It is stopped.
161s It is enabled.
161s Provides: test-loaded
161s Will not be respawned.
161s + herd -s t-socket-2611 status test-loaded
161s + grep stopped
161s It is stopped.
161s + herd -s t-socket-2611 start test-loaded
161s Greek letter λ
161s Service test-loaded has been started.
161s + herd -s t-socket-2611 status test-loaded
161s + grep -i running.*abc
161s Running value is abc.
161s + grep Greek letter t-log-2611
161s 2025-05-02 03:31:44 Greek letter λ
161s + herd -s t-socket-2611 stop test-loaded
161s + herd -s t-socket-2611 unload root test-loaded
161s Removing service 'test-loaded'...
161s Service test-loaded is not running.
161s Done.
161s + type -P pwd
161s + cat
161s + herd -s t-socket-2611 load root t-confdir-2611/some-conf.scm
161s Loading t-confdir-2611/some-conf.scm.
161s + herd -s t-socket-2611 start test-run-from-nonexistent-directory
161s Starting service test-run-from-nonexistent-directory...
161s Service test-run-from-nonexistent-directory started.
161s Service test-run-from-nonexistent-directory running with value #< id: 2883 command: ("-P: not found\npwd is a shell builtin")>.
161s Service test-run-from-nonexistent-directory has been started.
161s + herd -s t-socket-2611 status test-run-from-nonexistent-directory
161s + grep exited with code 127
161s Process exited with code 127.
161s + seq 1 10
161s + herd -s t-socket-2611 eval root (getpid)
161s + grep ^[0-9]
161s + test 2622 -eq 2622
161s + herd -s t-socket-2611 eval root (getpid)
161s + grep ^[0-9]
161s + test 2622 -eq 2622
161s + herd -s t-socket-2611 eval root (getpid)
161s + grep ^[0-9]
161s + test 2622 -eq 2622
161s + herd -s t-socket-2611 eval root (getpid)
161s + grep ^[0-9]
161s + test 2622 -eq 2622
161s + herd -s t-socket-2611 eval root (getpid)
161s + grep ^[0-9]
161s + test 2622 -eq 2622
161s + + herdgrep ^[0-9]
161s -s t-socket-2611 eval root (getpid)
162s + test 2622 -eq 2622
162s + herd -s t-socket-2611 eval root (getpid)
162s + grep ^[0-9]
162s + test 2622 -eq 2622
162s + herd -s t-socket-2611 eval root (getpid)
162s + grep ^[0-9]
162s + test 2622 -eq 2622
162s + + grep ^[0-9]
162s herd -s t-socket-2611 eval root (getpid)
162s + test 2622 -eq 2622
162s + + herd -s t-socket-2611 eval root (getpid)
162s grep ^[0-9]
162s + test 2622 -eq 2622
162s + herd -s t-socket-2611 unload root test-run-from-nonexistent-directory
162s Removing service 'test-run-from-nonexistent-directory'...
162s Service test-run-from-nonexistent-directory is not running.
162s Done.
162s + cat
162s + herd -s t-socket-2611 load root t-confdir-2611/some-conf.scm
162s Loading t-confdir-2611/some-conf.scm.
162s + herd -s t-socket-2611 start test-loaded
162s Starting service test-loaded...
162s Service test-loaded started.
162s Service test-loaded running with value #.
162s Service test-loaded has been started.
162s + herd -s t-socket-2611 status test-loaded
162s + grep -i running.*#
162s Running value is "#".
162s + herd -s t-socket-2611 stop test-loaded
162s + herd -s t-socket-2611 eval root (perform-service-action root-service 'unload "test-loaded")
162s Evaluating user expression (perform-service-action root-service (quote #) #).
162s Removing service 'test-loaded'...
162s Service test-loaded is not running.
162s Done.
162s "#"
162s + herd -s t-socket-2611 status test-loaded
162s herd: error: service 'test-loaded' could not be found
162s + true
162s + cat
162s + herd -s t-socket-2611 load root t-confdir-2611/some-conf.scm
162s Loading t-confdir-2611/some-conf.scm.
162s herd: error: exception caught while executing 'load' on service 'root':
162s Syntax error:
162s unknown location: source expression failed to match any pattern in form (define x y z)
162s + true
162s + herd -s t-socket-2611 status
162s Started:
162s + root
162s Stopped:
162s - broken
162s - spawn-with-system
162s - test
162s - test-2
162s + cat
162s + herd -s t-socket-2611 load root t-confdir-2611/some-conf.scm
162s Loading t-confdir-2611/some-conf.scm.
162s herd: error: exception caught while executing 'load' on service 'root':
162s Throw to key `what?!' with args `("#<>")'.
162s + true
162s + herd -s t-socket-2611 status
162s Started:
162s + root
162s Stopped:
162s - broken
162s - spawn-with-system
162s - test
162s - test-2
162s + herd -s t-socket-2611 eval root (/ 0 0)
162s Evaluating user expression (/ 0 0).
162s herd: error: exception caught while executing 'eval' on service 'root':
162s Throw to key `numerical-overflow' with args `("divide" "Numerical overflow" #f #f)'.
162s + true
162s + herd -s t-socket-2611 eval root (no closing paren
162s herd: error: exception caught while executing 'eval' on service 'root':
162s #:1:18: unexpected end of input while searching for: #\)
162s + true
162s + herd -s t-socket-2611 eval root (values)
162s + herd -s t-socket-2611 eval root ((@ (fibers) sleep) 1)
162s Evaluating user expression (values).
162s "#"
163s Evaluating user expression ((@ (fibers) sleep) 1).
163s "#"
163s + herd -s t-socket-2611 unload root all
163s Service broken is not running.
163s Service spawn-with-system is not running.
163s Service test-2 is not running.
163s Service test is not running.
163s + herd -s t-socket-2611 status
163s + grep Stopped:
163s + true
163s + herd -s t-socket-2611 status
163s + grep -e + root
163s + root
163s + grep already running t-log-2611
163s + true
163s + herd -s t-socket-2611 start root
163s + grep already running
163s Service root is already running.
163s + grep already running t-log-2611
163s 2025-05-02 03:31:46 Service root is already running.
163s + herd -s t-socket-2611 stop root
163s Stopping service root...
163s Exiting.
163s + kill -0 2622
163s tests/basic.sh: 332: kill: No such process
163s
163s + test -f t-log-2611
163s + export XDG_CONFIG_HOME=t-confdir-2611
163s + export XDG_DATA_HOME=t-datadir-2611
163s + export XDG_STATE_HOME=t-datadir-2611
163s + mkdir -p t-confdir-2611/shepherd
163s + mkdir -p t-datadir-2611/shepherd
163s + mv t-conf-2611 t-confdir-2611/shepherd/init.scm
163s + rm -f t-pid-2611 t-socket-2611
163s + + shepherd -I -s t-socket-2611 --pid=t-pid-2611
163s test -f t-pid-2611
163s + sleep 0.3
163s GNU Shepherd 1.0.2 (Guile 3.0.10, aarch64-unknown-linux-gnu)
163s Starting service root...
163s Service root started.
163s Service root running with value #< id: 3014 command: #f>.
163s Service root has been started.
163s Configuration successfully loaded from 't-confdir-2611/shepherd/init.scm'.
164s + test -f t-pid-2611
164s + herd -s t-socket-2611 start test
164s Starting service test...
164s Service test started.
164s Service test running with value #t.
164s Service test has been started.
164s + test -f t-stamp-2611
164s + herd -s t-socket-2611 status test
164s + grep running
164s It is running since 03:31:46 (0 seconds ago).
164s + herd -s t-socket-2611 stop test
164s + test -f t-stamp-2611
164s + cat t-pid-2611
164s + shepherd_pid=3014
164s + herd -s t-socket-2611 stop root
164s Stopping service root...
164s Exiting.
164s + kill -0 3014
164s tests/basic.sh: 369: kill: No such process
164s
164s + rm -rf t-confdir-2611 t-datadir-2611
164s + cat t-log-2611
164s + rm -f t-socket-2611 t-conf-2611 t-stamp-2611 t-log-2611
164s 2025-05-02 03:31:41 GNU Shepherd 1.0.2 (Guile 3.0.10, aarch64-unknown-linux-gnu)
164s 2025-05-02 03:31:41 Starting service root...
164s 2025-05-02 03:31:41 Service root started.
164s 2025-05-02 03:31:41 Service root running with value #< id: 2622 command: #f>.
164s 2025-05-02 03:31:41 Service root has been started.
164s 2025-05-02 03:31:41 Configuration successfully loaded from 't-conf-2611'.
164s 2025-05-02 03:31:42 Starting service test...
164s 2025-05-02 03:31:42 Service test has been started.
164s 2025-05-02 03:31:42 Service test started.
164s 2025-05-02 03:31:42 Service test running with value #t.
164s 2025-05-02 03:31:42 Stopping service test...
164s 2025-05-02 03:31:42 Service test might have failed to stop.
164s 2025-05-02 03:31:42 Service test is now stopped.
164s 2025-05-02 03:31:42 Disabled service test-2.
164s 2025-05-02 03:31:42 Starting service test...
164s 2025-05-02 03:31:42 Service test has been started.
164s 2025-05-02 03:31:42 Service test started.
164s 2025-05-02 03:31:42 Service test running with value #t.
164s 2025-05-02 03:31:42 Service test-2 is currently disabled.
164s 2025-05-02 03:31:42 Service test-2 is currently disabled.
164s 2025-05-02 03:31:42 Enabled service test-2.
164s 2025-05-02 03:31:42 Starting service test-2...
164s 2025-05-02 03:31:42 Service test-2 has been started.
164s 2025-05-02 03:31:42 Service test-2 started.
164s 2025-05-02 03:31:42 Service test-2 running with value #t.
164s 2025-05-02 03:31:42 hi: Say hi.
164s 2025-05-02 03:31:42 start
164s 2025-05-02 03:31:42
164s 2025-05-02 03:31:42 end
164s 2025-05-02 03:31:42 start
164s 2025-05-02 03:31:42
164s 2025-05-02 03:31:42 end
164s 2025-05-02 03:31:42 start
164s 2025-05-02 03:31:42
164s 2025-05-02 03:31:42 end
164s 2025-05-02 03:31:42 start
164s 2025-05-02 03:31:42
164s 2025-05-02 03:31:42 end
164s 2025-05-02 03:31:43 Starting service broken...
164s 2025-05-02 03:31:43 Service broken failed to start.
164s 2025-05-02 03:31:43 Starting service spawn-with-system...
164s 2025-05-02 03:31:43 [bash] starting from /tmp/autopkgtest.482nKi/build.ox0/src
164s 2025-05-02 03:31:43 Service spawn-with-system has been started.
164s 2025-05-02 03:31:43 Service spawn-with-system started.
164s 2025-05-02 03:31:43 Service spawn-with-system running with value #t.
164s 2025-05-02 03:31:43 Stopping service spawn-with-system...
164s 2025-05-02 03:31:43 Registering new logger for spawn-with-system.
164s 2025-05-02 03:31:43 [bash] stopping from /tmp/autopkgtest.482nKi/build.ox0/src
164s 2025-05-02 03:31:43 Service spawn-with-system stopped.
164s 2025-05-02 03:31:43 Service spawn-with-system is now stopped.
164s 2025-05-02 03:31:43 status: Return an s-expression showing information about all the services.
164s 2025-05-02 03:31:43 Clients such as 'herd' can read it and format it in a human-readable way.
164s 2025-05-02 03:31:43 help:
164s 2025-05-02 03:31:43 Show the help message for the 'root' service.
164s 2025-05-02 03:31:43
164s 2025-05-02 03:31:43 status:
164s 2025-05-02 03:31:43 Return an s-expression showing information about all the services.
164s 2025-05-02 03:31:43 Clients such as 'herd' can read it and format it in a human-readable way.
164s 2025-05-02 03:31:43
164s 2025-05-02 03:31:43 halt:
164s 2025-05-02 03:31:43 Halt the system.
164s 2025-05-02 03:31:43
164s 2025-05-02 03:31:43 power-off:
164s 2025-05-02 03:31:43 Halt the system and turn it off.
164s 2025-05-02 03:31:43
164s 2025-05-02 03:31:43 kexec:
164s 2025-05-02 03:31:43 Reboot the system and run kexec.
164s 2025-05-02 03:31:43
164s 2025-05-02 03:31:43 load:
164s 2025-05-02 03:31:43 Load the Scheme code from FILE into shepherd. This is potentially
164s 2025-05-02 03:31:43 dangerous. You have been warned.
164s 2025-05-02 03:31:43
164s 2025-05-02 03:31:43 eval:
164s 2025-05-02 03:31:43 Evaluate the given Scheme expression into the shepherd. This is
164s 2025-05-02 03:31:43 potentially dangerous, be careful.
164s 2025-05-02 03:31:43
164s 2025-05-02 03:31:43 unload:
164s 2025-05-02 03:31:43 Unload the service identified by SERVICE-NAME or all services
164s 2025-05-02 03:31:43 except for 'root' if SERVICE-NAME is 'all'. Stop services before
164s 2025-05-02 03:31:43 removing them if needed.
164s 2025-05-02 03:31:43
164s 2025-05-02 03:31:43 reload:
164s 2025-05-02 03:31:43 Unload all services, then load from FILE-NAME into shepherd. This
164s 2025-05-02 03:31:43 is potentially dangerous. You have been warned.
164s 2025-05-02 03:31:43
164s 2025-05-02 03:31:43 daemonize:
164s 2025-05-02 03:31:43 Go into the background. Be careful, this means that a new
164s 2025-05-02 03:31:43 process will be created, so shepherd will not get SIGCHLD signals anymore
164s 2025-05-02 03:31:43 if previously spawned children terminate. Therefore, this action should
164s 2025-05-02 03:31:43 usually only be used (if at all) *before* children get spawned for which
164s 2025-05-02 03:31:43 we want to receive these signals.
164s 2025-05-02 03:31:43
164s 2025-05-02 03:31:43 restart:
164s 2025-05-02 03:31:43 This does not work for the 'root' service.
164s 2025-05-02 03:31:43
164s 2025-05-02 03:31:43 help:
164s 2025-05-02 03:31:43 Show the help message for the 'root' service.
164s 2025-05-02 03:31:43
164s 2025-05-02 03:31:43 status:
164s 2025-05-02 03:31:43 Return an s-expression showing information about all the services.
164s 2025-05-02 03:31:43 Clients such as 'herd' can read it and format it in a human-readable way.
164s 2025-05-02 03:31:43
164s 2025-05-02 03:31:43 halt:
164s 2025-05-02 03:31:43 Halt the system.
164s 2025-05-02 03:31:43
164s 2025-05-02 03:31:43 power-off:
164s 2025-05-02 03:31:43 Halt the system and turn it off.
164s 2025-05-02 03:31:43
164s 2025-05-02 03:31:43 kexec:
164s 2025-05-02 03:31:43 Reboot the system and run kexec.
164s 2025-05-02 03:31:43
164s 2025-05-02 03:31:43 load:
164s 2025-05-02 03:31:43 Load the Scheme code from FILE into shepherd. This is potentially
164s 2025-05-02 03:31:43 dangerous. You have been warned.
164s 2025-05-02 03:31:43
164s 2025-05-02 03:31:43 eval:
164s 2025-05-02 03:31:43 Evaluate the given Scheme expression into the shepherd. This is
164s 2025-05-02 03:31:43 potentially dangerous, be careful.
164s 2025-05-02 03:31:43
164s 2025-05-02 03:31:43 unload:
164s 2025-05-02 03:31:43 Unload the service identified by SERVICE-NAME or all services
164s 2025-05-02 03:31:43 except for 'root' if SERVICE-NAME is 'all'. Stop services before
164s 2025-05-02 03:31:43 removing them if needed.
164s 2025-05-02 03:31:43
164s 2025-05-02 03:31:43 reload:
164s 2025-05-02 03:31:43 Unload all services, then load from FILE-NAME into shepherd. This
164s 2025-05-02 03:31:43 is potentially dangerous. You have been warned.
164s 2025-05-02 03:31:43
164s 2025-05-02 03:31:43 daemonize:
164s 2025-05-02 03:31:43 Go into the background. Be careful, this means that a new
164s 2025-05-02 03:31:43 process will be created, so shepherd will not get SIGCHLD signals anymore
164s 2025-05-02 03:31:43 if previously spawned children terminate. Therefore, this action should
164s 2025-05-02 03:31:43 usually only be used (if at all) *before* children get spawned for which
164s 2025-05-02 03:31:43 we want to receive these signals.
164s 2025-05-02 03:31:43
164s 2025-05-02 03:31:43 restart:
164s 2025-05-02 03:31:43 This does not work for the 'root' service.
164s 2025-05-02 03:31:43
164s 2025-05-02 03:31:43 Loading /does/not/exist.scm.
164s 2025-05-02 03:31:43 Removing service 'broken'...
164s 2025-05-02 03:31:43 Service broken is not running.
164s 2025-05-02 03:31:43 Done.
164s 2025-05-02 03:31:43 Removing service 'test'...
164s 2025-05-02 03:31:43 Stopping service test-2...
164s 2025-05-02 03:31:43 Service test-2 might have failed to stop.
164s 2025-05-02 03:31:43 Service test-2 is now stopped.
164s 2025-05-02 03:31:43 Stopping service test...
164s 2025-05-02 03:31:43 Service test might have failed to stop.
164s 2025-05-02 03:31:43 Service test is now stopped.
164s 2025-05-02 03:31:43 Done.
164s 2025-05-02 03:31:43 Service test-2 is not running.
164s 2025-05-02 03:31:43 Service spawn-with-system is not running.
164s 2025-05-02 03:31:43 Loading t-conf-2611.
164s 2025-05-02 03:31:43 Loading t-confdir-2611/some-conf.scm.
164s 2025-05-02 03:31:43 Passing 'register-services' services as a rest list is now deprecated.
164s 2025-05-02 03:31:44 Starting service test-loaded...
164s 2025-05-02 03:31:44 Greek letter λ
164s 2025-05-02 03:31:44 Service test-loaded has been started.
164s 2025-05-02 03:31:44 Service test-loaded started.
164s 2025-05-02 03:31:44 Service test-loaded running with value abc.
164s 2025-05-02 03:31:44 Stopping service test-loaded...
164s 2025-05-02 03:31:44 Service test-loaded stopped.
164s 2025-05-02 03:31:44 Service test-loaded is now stopped.
164s 2025-05-02 03:31:44 Removing service 'test-loaded'...
164s 2025-05-02 03:31:44 Service test-loaded is not running.
164s 2025-05-02 03:31:44 Done.
164s 2025-05-02 03:31:44 Loading t-confdir-2611/some-conf.scm.
164s 2025-05-02 03:31:44 Starting service test-run-from-nonexistent-directory...
164s 2025-05-02 03:31:44 Service test-run-from-nonexistent-directory started.
164s 2025-05-02 03:31:44 Failed to run "-P: not found\npwd is a shell builtin": In procedure chdir: No such file or directory
164s 2025-05-02 03:31:44 Service test-run-from-nonexistent-directory running with value #< id: 2883 command: ("-P: not found\npwd is a shell builtin")>.
164s 2025-05-02 03:31:44 Service test-run-from-nonexistent-directory has been started.
164s 2025-05-02 03:31:44 Service test-run-from-nonexistent-directory (PID 2883) exited with 127.
164s 2025-05-02 03:31:44 Service test-run-from-nonexistent-directory has been disabled.
164s 2025-05-02 03:31:44 Evaluating user expression (getpid).
164s 2025-05-02 03:31:44 Evaluating user expression (getpid).
164s 2025-05-02 03:31:44 Evaluating user expression (getpid).
164s 2025-05-02 03:31:44 Evaluating user expression (getpid).
164s 2025-05-02 03:31:44 Evaluating user expression (getpid).
164s 2025-05-02 03:31:44 Evaluating user expression (getpid).
164s 2025-05-02 03:31:44 Evaluating user expression (getpid).
164s 2025-05-02 03:31:44 Evaluating user expression (getpid).
164s 2025-05-02 03:31:44 Evaluating user expression (getpid).
164s 2025-05-02 03:31:44 Evaluating user expression (getpid).
164s 2025-05-02 03:31:44 Removing service 'test-run-from-nonexistent-directory'...
164s 2025-05-02 03:31:44 Service test-run-from-nonexistent-directory is not running.
164s 2025-05-02 03:31:44 Done.
164s 2025-05-02 03:31:44 Loading t-confdir-2611/some-conf.scm.
164s 2025-05-02 03:31:44 Starting service test-loaded...
164s 2025-05-02 03:31:44 Service test-loaded started.
164s 2025-05-02 03:31:44 Service test-loaded running with value #.
164s 2025-05-02 03:31:44 Service test-loaded has been started.
164s 2025-05-02 03:31:44 Stopping service test-loaded...
164s 2025-05-02 03:31:44 Service test-loaded stopped.
164s 2025-05-02 03:31:44 Service test-loaded is now stopped.
164s 2025-05-02 03:31:44 Evaluating user expression (perform-service-action root-service (quote #) #).
164s 2025-05-02 03:31:44 Removing service 'test-loaded'...
164s 2025-05-02 03:31:44 Service test-loaded is not running.
164s 2025-05-02 03:31:44 Done.
164s 2025-05-02 03:31:44 Loading t-confdir-2611/some-conf.scm.
164s 2025-05-02 03:31:44 Loading t-confdir-2611/some-conf.scm.
164s 2025-05-02 03:31:44 Evaluating user expression (/ 0 0).
164s 2025-05-02 03:31:44 Evaluating user expression (values).
164s 2025-05-02 03:31:44 Evaluating user expression ((@ (fibers) sleep) 1).
164s 2025-05-02 03:31:45 Service broken is not running.
164s 2025-05-02 03:31:45 Service spawn-with-system is not running.
164s 2025-05-02 03:31:45 Service test-2 is not running.
164s 2025-05-02 03:31:45 Service test is not running.
164s 2025-05-02 03:31:46 Service root is already running.
164s 2025-05-02 03:31:46 Stopping service root...
164s + test -f t-pid-2611
164s + cat t-pid-2611
164s + kill 3014
164s tests/basic.sh: 2: kill: No such process
164s
164s + true
164s + rm -f t-pid-2611
164s autopkgtest [03:31:46]: test tests-basic: -----------------------]
164s autopkgtest [03:31:46]: test tests-basic: - - - - - - - - - - results - - - - - - - - - -
164s tests-basic PASS
165s autopkgtest [03:31:47]: test tests-starting-status: preparing testbed
165s Reading package lists...
165s Building dependency tree...
165s Reading state information...
165s Starting pkgProblemResolver with broken count: 0
165s Starting 2 pkgProblemResolver with broken count: 0
165s Done
166s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
167s autopkgtest [03:31:49]: test tests-starting-status: sh -x tests/starting-status.sh
167s autopkgtest [03:31:49]: test tests-starting-status: [-----------------------
167s + shepherd --version
167s shepherd (GNU Shepherd) 1.0.2
167s Copyright (C) 2025 the Shepherd authors
167s License GPLv3+: GNU GPL version 3 or later
167s This is free software: you are free to change and redistribute it.
167s There is NO WARRANTY, to the extent permitted by law.
167s + herd --version
167s herd (GNU Shepherd) 1.0.2
167s Copyright (C) 2025 the Shepherd authors
167s License GPLv3+: GNU GPL version 3 or later
167s This is free software: you are free to change and redistribute it.
167s There is NO WARRANTY, to the extent permitted by law.
167s + socket=t-socket-3189
167s + conf=t-conf-3189
167s + confdir=t-confdir-3189
167s + datadir=t-datadir-3189
167s + log=t-log-3189
167s + stamp=t-stamp-3189
167s + pid=t-pid-3189
167s + herd=herd -s t-socket-3189
167s + trap cat t-log-3189 || true; rm -f t-socket-3189 t-conf-3189 t-stamp-3189 t-log-3189;
167s test -f t-pid-3189 && kill `cat t-pid-3189` || true; rm -f t-pid-3189 EXIT
167s + cat
167s + rm -f t-pid-3189 t-stamp-3189
167s + test -f t-pid-3189
167s + sleep 0.3
167s + shepherd -I -s t-socket-3189 -c t-conf-3189 -l t-log-3189 --pid=t-pid-3189
167s GNU Shepherd 1.0.2 (Guile 3.0.10, aarch64-unknown-linux-gnu)
167s Starting service root...
167s Service root started.
167s Service root running with value #< id: 3200 command: #f>.
167s Service root has been started.
167s Configuration successfully loaded from 't-conf-3189'.
167s + test -f t-pid-3189
167s + cat t-pid-3189
167s + shepherd_pid=3200
167s + herd_pid=3208
167s + herd -s t-socket-3189 status
167s + herd -s t-socket-3189 start test
167s Started:
167s + root
167s Starting:
167s ^ test
167s + herd+ -sgrep ^ test
167s t-socket-3189 status
167s ^ test
167s + herd -s t-socket-3189 status test
168s ● Status of test:
168s It is starting.
168s It is enabled.
168s Provides: test
168s Will not be respawned.
168s + herd -s t-socket-3189 status test
168s + grep starting
168s It is starting.
168s + herd_pid2=3225
168s + sleep 1
168s + herd -s t-socket-3189 start test
169s + kill -0 3208
169s + kill -0 3225
169s + touch t-stamp-3189
169s + n=0
169s + :
169s + herd -s t-socket-3189 status test
169s + grep running
169s + expr 0 + 1
169s + n=1
169s + test 1 -le 10
169s + sleep 1
169s Starting service test...
169s Service test has been started.
170s + :
170s + herd -s t-socket-3189 status test
170s + grep running
170s It is running since 03:31:52 (0 seconds ago).
170s + break
170s + n=0
170s + :
170s + kill -0 3208
170s tests/starting-status.sh: 91: kill: No such process
170s
170s + kill -0 3225
170s tests/starting-status.sh: 91: kill: No such process
170s
170s + break
170s + herd -s t-socket-3189 stop test
170s + test -f t-stamp-3189
170s + Now trying to stop a service in 'starting' state.
170s + wc -l
170s grep Starting service test t-log-3189
170s + test 1 = 1
170s + echo Now trying to stop a service in 'starting' state.
170s + herd -s t-socket-3189 start test
170s + herd_start_pid=3247
170s + herd -s t-socket-3189 status test
170s + grep starting
170s It is starting.
170s + herd_stop_pid1=3254
170s + herd_stop_pid2=3255
170s + herd -s+ herd -s t-socket-3189 stop test
170s t-socket-3189 stop test
170s + seq 1 3
170s + herd -s t-socket-3189 status test
170s + grep starting
170s It is starting.
170s + sleep 0.3
170s + herd -s t-socket-3189 status test
170s + grep starting
170s + sleep 0.3
170s It is starting.
170s + herd -s t-socket-3189 status test
170s + grep starting
170s + sleep 0.3
170s It is starting.
171s + grep Waiting for test to start t-log-3189
171s 2025-05-02 03:31:52 Waiting for test to start...
171s 2025-05-02 03:31:52 Waiting for test to start...
171s + touch t-stamp-3189
171s + kill -0 3247
171s + sleep 0.5
171s + kill -0 3247
171s + sleep 0.5
172s Service test has been started.
172s + kill -0 3247
172s tests/starting-status.sh: 131: kill: No such process
172s
172s + kill -0 3254
172s tests/starting-status.sh: 132: kill: No such process
172s
172s + kill -0 3255
172s tests/starting-status.sh: 133: kill: No such process
172s
172s + herd -s t-socket-3189 status test
172s + grep stopped
172s It is stopped since 03:31:54 (0 seconds ago).
172s + herd -s t-socket-3189 stop root
172s Stopping service root...
172s Exiting.
172s + rm -rf t-confdir-3189
172s + rm -rf t-datadir-3189
172s + cat t-log-3189
172s 2025-05-02 03:31:50 GNU Shepherd 1.0.2 (Guile 3.0.10, aarch64-unknown-linux-gnu)
172s 2025-05-02 03:31:50 Starting service root...
172s 2025-05-02 03:31:50 Service root started.
172s 2025-05-02 03:31:50 Service root running with value #< id: 3200 command: #f>.
172s 2025-05-02 03:31:50 Service root has been started.
172s 2025-05-02 03:31:50 Configuration successfully loaded from 't-conf-3189'.
172s 2025-05-02 03:31:50 Starting service test...
172s 2025-05-02 03:31:52 Service test has been started.
172s 2025-05-02 03:31:52 Service test started.
172s 2025-05-02 03:31:52 Service test running with value #t.
172s 2025-05-02 03:31:52 Stopping service test...
172s 2025-05-02 03:31:52 Service test might have failed to stop.
172s 2025-05-02 03:31:52 Service test is now stopped.
172s 2025-05-02 03:31:52 Starting service test...
172s 2025-05-02 03:31:52 Waiting for test to start...
172s 2025-05-02 03:31:52 Waiting for test to start...
172s 2025-05-02 03:31:54 Service test has been started.
172s 2025-05-02 03:31:54 Service test started.
172s 2025-05-02 03:31:54 Service test running with value #t.
172s 2025-05-02 03:31:54 Stopping service test...
172s 2025-05-02 03:31:54 Service test might have failed to stop.
172s 2025-05-02 03:31:54 Service test is now stopped.
172s 2025-05-02 03:31:54 Stopping service root...
172s 2025-05-02 03:31:54 Exiting shepherd...
172s + rm -f t-socket-3189 t-conf-3189 t-stamp-3189 t-log-3189
172s + test -f t-pid-3189
172s + cat t-pid-3189
172s + kill 3200
172s tests/starting-status.sh: 2: kill: No such process
172s
172s + true
172s + rm -f t-pid-3189
172s autopkgtest [03:31:54]: test tests-starting-status: -----------------------]
172s autopkgtest [03:31:54]: test tests-starting-status: - - - - - - - - - - results - - - - - - - - - -
172s tests-starting-status PASS
173s autopkgtest [03:31:55]: test tests-one-shot: preparing testbed
173s Reading package lists...
173s Building dependency tree...
173s Reading state information...
174s Starting pkgProblemResolver with broken count: 0
174s Starting 2 pkgProblemResolver with broken count: 0
174s Done
174s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
175s autopkgtest [03:31:57]: test tests-one-shot: sh -x tests/one-shot.sh
175s autopkgtest [03:31:57]: test tests-one-shot: [-----------------------
175s + shepherd --version
175s shepherd (GNU Shepherd) 1.0.2
175s Copyright (C) 2025 the Shepherd authors
175s License GPLv3+: GNU GPL version 3 or later
175s This is free software: you are free to change and redistribute it.
175s There is NO WARRANTY, to the extent permitted by law.
175s + herd --version
175s herd (GNU Shepherd) 1.0.2
175s Copyright (C) 2025 the Shepherd authors
175s License GPLv3+: GNU GPL version 3 or later
175s This is free software: you are free to change and redistribute it.
175s There is NO WARRANTY, to the extent permitted by law.
175s + socket=t-socket-3441
175s + conf=t-conf-3441
175s + confdir=t-confdir-3441
175s + log=t-log-3441
175s + stamp=t-stamp-3441
175s + pid=t-pid-3441
175s + herd=herd -s t-socket-3441
175s + trap cat t-log-3441 || true; rm -f t-socket-3441 t-conf-3441 t-stamp-3441 t-log-3441;
175s test -f t-pid-3441 && kill `cat t-pid-3441` || true; rm -f t-pid-3441 EXIT
175s + cat
175s + rm -f t-pid-3441
175s + + shepherd -I -s t-socket-3441 -c t-conf-3441 -l t-log-3441 --pid=t-pid-3441
175s test -f t-pid-3441
175s + sleep 0.3
175s GNU Shepherd 1.0.2 (Guile 3.0.10, aarch64-unknown-linux-gnu)
175s Starting service root...
175s Service root started.
175s Service root running with value #< id: 3452 command: #f>.
175s Service root has been started.
175s Configuration successfully loaded from 't-conf-3441'.
175s Starting service one-shotty...
175s Service one-shotty started.
175s Service one-shotty running with value #t.
175s Service one-shotty has been started.
175s Starting service a...
175s Service a started.
175s Service a running with value #t.
175s Service a has been started.
175s Starting service b...
175s Service b started.
176s Service b running with value #t.
176s Service b has been started.
176s Starting service c...
176s Service c started.
176s Service c running with value #t.
176s Service c has been started.
176s Successfully started 3 services in the background.
176s + test -f t-pid-3441
176s + cat t-pid-3441
176s + shepherd_pid=3452
176s + kill -0 3452
176s + test -S t-socket-3441
176s + herd -s t-socket-3441 start always-fail
176s Starting service always-fail...
176s Service always-fail failed to start.
176s Service always-fail could not be started.
176s herd: error: failed to start service always-fail
176s + true
176s + rm -f t-stamp-3441
176s + herd -s t-socket-3441 start test
176s Starting service test...
176s Service test started.
176s Service test running with value #t.
176s Service test has been started.
176s + test -f t-stamp-3441
176s + herd -s t-socket-3441 status test
176s + grep stopped.*one-shot
176s It is stopped (one-shot).
176s 2025-05-02 03:31:58 Service test started.
176s 2025-05-02 03:31:58 Service test has been started.
176s + grep test.*started t-log-3441
176s + herd -s t-socket-3441 stop test
176s + rm -f t-stamp-3441
176s + herd -s t-socket-3441 start test
176s Service test has been started.
176s + test -f t-stamp-3441
176s + herd -s t-socket-3441 status test
176s + grep stopped.*one-shot
176s It is stopped (one-shot).
176s + grep test.*started t-log-3441
176s + herd2025-05-02 03:31:58 Service test started.
176s 2025-05-02 03:31:58 Service test has been started.
176s 2025-05-02 03:31:58 Service test has been started.
176s 2025-05-02 03:31:58 Service test started.
176s -s t-socket-3441 stop test
176s + rm -f t-stamp-3441
176s + herd -s t-socket-3441 start test
176s Service test has been started.
176s + test -f t-stamp-3441
176s + herd -s t-socket-3441 status test
176s + grep stopped.*one-shot
176s It is stopped (one-shot).
176s + grep test.*started t-log-3441
176s 2025-05-02 03:31:58 Service test started.
176s 2025-05-02 03:31:58 Service test has been started.
176s 2025-05-02 03:31:58 Service test has been started.
176s 2025-05-02 03:31:58 Service test started.
176s 2025-05-02 03:31:58 Service test has been started.
176s 2025-05-02 03:31:58 Service test started.
176s + herd -s t-socket-3441 stop test
176s + herd -s t-socket-3441 status
176s + grep -i ^one-shot
176s One-shot:
176s + herd -s t-socket-3441 status
176s Started:
176s + a
176s + b
176s + c
176s + root
176s Stopped:
176s - test-2
176s One-shot:
176s * always-fail
176s * one-shotty
176s * test
176s + rm -f t-stamp-3441 t-stamp-3441-2
176s + herd -s t-socket-3441 start test-2
176s Service test has been started.
176s Service test-2 has been started.
176s + test -f t-stamp-3441
176s + test -f t-stamp-3441-2
176s + herd -s t-socket-3441 status test
176s + grep stopped.*one-shot
176s It is stopped (one-shot).
176s + + grep running
176s herd -s t-socket-3441 status test-2
176s + It is running since 03:31:58 (0 seconds ago).
176s herd -s t-socket-3441 stop test-2
176s + test -f t-stamp-3441-2
176s + true
176s + grep+ wc -l
176s Starting service one-shotty t-log-3441
176s + test 1 -eq 1
176s + herd -s t-socket-3441 stop a
176s Stopping service c...
176s Service c stopped.
176s Service c is now stopped.
176s Stopping service b...
176s Service b stopped.
176s Service b is now stopped.
176s Stopping service a...
176s Service a stopped.
176s Service a is now stopped.
176s + herd -s t-socket-3441 start c
176s Starting service one-shotty...
176s Service one-shotty started.
176s Service one-shotty running with value #t.
176s Starting service a...
176s Service a started.
176s Service a running with value #t.
176s Starting service b...
176s Service b started.
176s Service b running with value #t.
176s Starting service c...
176s Service c started.
176s Service c running with value #t.
176s Service one-shotty has been started.
176s Service a has been started.
176s Service b has been started.
176s Service c has been started.
176s + grep+ Starting service one-shotty t-log-3441
176s wc -l
176s + test 2 -eq 2
176s + herd -s t-socket-3441 stop a
176s Stopping service c...
176s Service c stopped.
176s Service c is now stopped.
176s Stopping service b...
176s Service b stopped.
176s Service b is now stopped.
176s Stopping service a...
176s Service a stopped.
176s Service a is now stopped.
176s + herd -s t-socket-3441 start c
176s Starting service one-shotty...
176s Service one-shotty started.
176s Service one-shotty running with value #t.
176s Starting service a...
176s Service a started.
176s Service a running with value #t.
176s Starting service b...
176s Service b started.
176s Service b running with value #t.
176s Starting service c...
176s Service c started.
176s Service c running with value #t.
176s Service one-shotty has been started.
176s Service a has been started.
176s Service b has been started.
176s Service c has been started.
176s + grep Starting service one-shotty t-log-3441
176s + wc -l
176s + test 3 -eq 3
176s + herd -s t-socket-3441 start one-shotty
176s Starting service one-shotty...
176s Service one-shotty started.
176s Service one-shotty running with value #t.
176s Service one-shotty has been started.
176s + grep Starting service one-shotty t-log-3441
176s + wc -l
176s + test 4 -eq 4
176s + cat
176s + rm -f t-stamp-3441
176s + herd -s t-socket-3441 load root t-conf-3441
176s Loading t-conf-3441.
176s + grep Service third started t-log-3441
176s + sleep 0.5
177s + grep Service third started t-log-3441
177s + sleep 0.5
177s + grep Service third started t-log-3441
177s + sleep 0.5
178s + grep Service third started t-log-3441
178s + sleep 0.5
178s + grep Service third started t-log-3441
178s 2025-05-02 03:32:01 Service third started.
178s + cat t-stamp-3441
178s + test third = third
178s + herd -s t-socket-3441 start fourth
178s Service always-fail could not be started.
178s Service fourth depends on always-fail.
178s herd: error: failed to start service fourth
178s + herd -s t-socket-3441 start fourth
178s Service always-fail could not be started.
178s Service fourth depends on always-fail.
178s herd: error: failed to start service fourth
178s + herd -s t-socket-3441 stop root
178s Stopping service root...
178s Stopping service c...
178s Service c stopped.
178s Service c is now stopped.
178s Stopping service b...
178s Service b stopped.
178s Service b is now stopped.
178s Stopping service a...
178s Service a stopped.
178s Service a is now stopped.
178s Exiting.
178s + cat t-log-3441
178s 2025-05-02 03:31:58 GNU Shepherd 1.0.2 (Guile 3.0.10, aarch64-unknown-linux-gnu)
178s 2025-05-02 03:31:58 Starting service root...
178s 2025-05-02 03:31:58 Service root started.
178s 2025-05-02 03:31:58 Service root running with value #< id: 3452 command: #f>.
178s 2025-05-02 03:31:58 Service root has been started.
178s 2025-05-02 03:31:58 Configuration successfully loaded from 't-conf-3441'.
178s 2025-05-02 03:31:58 Starting service one-shotty...
178s 2025-05-02 03:31:58 Service one-shotty started.
178s 2025-05-02 03:31:58 Service one-shotty running with value #t.
178s 2025-05-02 03:31:58 Service one-shotty has been started.
178s 2025-05-02 03:31:58 Starting service a...
178s 2025-05-02 03:31:58 Service a started.
178s 2025-05-02 03:31:58 Service a running with value #t.
178s 2025-05-02 03:31:58 Service a has been started.
178s 2025-05-02 03:31:58 Starting service b...
178s 2025-05-02 03:31:58 Service b started.
178s 2025-05-02 03:31:58 Service b running with value #t.
178s 2025-05-02 03:31:58 Service b has been started.
178s 2025-05-02 03:31:58 Starting service c...
178s 2025-05-02 03:31:58 Service c started.
178s 2025-05-02 03:31:58 Service c running with value #t.
178s 2025-05-02 03:31:58 Service c has been started.
178s 2025-05-02 03:31:58 Successfully started 3 services in the background.
178s 2025-05-02 03:31:58 Starting service always-fail...
178s 2025-05-02 03:31:58 Service always-fail failed to start.
178s 2025-05-02 03:31:58 Service always-fail could not be started.
178s 2025-05-02 03:31:58 Starting service test...
178s 2025-05-02 03:31:58 Service test started.
178s 2025-05-02 03:31:58 Service test running with value #t.
178s 2025-05-02 03:31:58 Service test has been started.
178s 2025-05-02 03:31:58 Starting service test...
178s 2025-05-02 03:31:58 Service test has been started.
178s 2025-05-02 03:31:58 Service test started.
178s 2025-05-02 03:31:58 Service test running with value #t.
178s 2025-05-02 03:31:58 Starting service test...
178s 2025-05-02 03:31:58 Service test has been started.
178s 2025-05-02 03:31:58 Service test started.
178s 2025-05-02 03:31:58 Service test running with value #t.
178s 2025-05-02 03:31:58 Starting service test...
178s 2025-05-02 03:31:58 Service test has been started.
178s 2025-05-02 03:31:58 Service test started.
178s 2025-05-02 03:31:58 Service test running with value #t.
178s 2025-05-02 03:31:58 Starting service test-2...
178s 2025-05-02 03:31:58 Service test-2 has been started.
178s 2025-05-02 03:31:58 Service test-2 started.
178s 2025-05-02 03:31:58 Service test-2 running with value #t.
178s 2025-05-02 03:31:59 Stopping service test-2...
178s 2025-05-02 03:31:59 Service test-2 stopped.
178s 2025-05-02 03:31:59 Service test-2 is now stopped.
178s 2025-05-02 03:31:59 Stopping service c...
178s 2025-05-02 03:31:59 Service c stopped.
178s 2025-05-02 03:31:59 Service c is now stopped.
178s 2025-05-02 03:31:59 Stopping service b...
178s 2025-05-02 03:31:59 Service b stopped.
178s 2025-05-02 03:31:59 Service b is now stopped.
178s 2025-05-02 03:31:59 Stopping service a...
178s 2025-05-02 03:31:59 Service a stopped.
178s 2025-05-02 03:31:59 Service a is now stopped.
178s 2025-05-02 03:31:59 Starting service one-shotty...
178s 2025-05-02 03:31:59 Service one-shotty has been started.
178s 2025-05-02 03:31:59 Service one-shotty started.
178s 2025-05-02 03:31:59 Service one-shotty running with value #t.
178s 2025-05-02 03:31:59 Starting service a...
178s 2025-05-02 03:31:59 Service a has been started.
178s 2025-05-02 03:31:59 Service a started.
178s 2025-05-02 03:31:59 Service a running with value #t.
178s 2025-05-02 03:31:59 Starting service b...
178s 2025-05-02 03:31:59 Service b has been started.
178s 2025-05-02 03:31:59 Service b started.
178s 2025-05-02 03:31:59 Service b running with value #t.
178s 2025-05-02 03:31:59 Starting service c...
178s 2025-05-02 03:31:59 Service c has been started.
178s 2025-05-02 03:31:59 Service c started.
178s 2025-05-02 03:31:59 Service c running with value #t.
178s 2025-05-02 03:31:59 Stopping service c...
178s 2025-05-02 03:31:59 Service c stopped.
178s 2025-05-02 03:31:59 Service c is now stopped.
178s 2025-05-02 03:31:59 Stopping service b...
178s 2025-05-02 03:31:59 Service b stopped.
178s 2025-05-02 03:31:59 Service b is now stopped.
178s 2025-05-02 03:31:59 Stopping service a...
178s 2025-05-02 03:31:59 Service a stopped.
178s 2025-05-02 03:31:59 Service a is now stopped.
178s 2025-05-02 03:31:59 Starting service one-shotty...
178s 2025-05-02 03:31:59 Service one-shotty has been started.
178s 2025-05-02 03:31:59 Service one-shotty started.
178s 2025-05-02 03:31:59 Service one-shotty running with value #t.
178s 2025-05-02 03:31:59 Starting service a...
178s 2025-05-02 03:31:59 Service a has been started.
178s 2025-05-02 03:31:59 Service a started.
178s 2025-05-02 03:31:59 Service a running with value #t.
178s 2025-05-02 03:31:59 Starting service b...
178s 2025-05-02 03:31:59 Service b has been started.
178s 2025-05-02 03:31:59 Service b started.
178s 2025-05-02 03:31:59 Service b running with value #t.
178s 2025-05-02 03:31:59 Starting service c...
178s 2025-05-02 03:31:59 Service c has been started.
178s 2025-05-02 03:31:59 Service c started.
178s 2025-05-02 03:31:59 Service c running with value #t.
178s 2025-05-02 03:31:59 Starting service one-shotty...
178s 2025-05-02 03:31:59 Service one-shotty has been started.
178s 2025-05-02 03:31:59 Service one-shotty started.
178s 2025-05-02 03:31:59 Service one-shotty running with value #t.
178s 2025-05-02 03:31:59 Loading t-conf-3441.
178s 2025-05-02 03:31:59 Starting service first...
178s 2025-05-02 03:32:00 Service first has been started.
178s 2025-05-02 03:32:00 Service first started.
178s 2025-05-02 03:32:00 Service first running with value #t.
178s 2025-05-02 03:32:00 Starting service second...
178s 2025-05-02 03:32:01 Service second has been started.
178s 2025-05-02 03:32:01 Service second started.
178s 2025-05-02 03:32:01 Service second running with value #t.
178s 2025-05-02 03:32:01 Starting service third...
178s 2025-05-02 03:32:01 Service third started.
178s 2025-05-02 03:32:01 Service third running with value #t.
178s 2025-05-02 03:32:01 Service third has been started.
178s 2025-05-02 03:32:01 Successfully started 3 services in the background.
178s 2025-05-02 03:32:01 Starting service always-fail...
178s 2025-05-02 03:32:01 Service always-fail could not be started.
178s 2025-05-02 03:32:01 Service always-fail failed to start.
178s 2025-05-02 03:32:01 Service fourth depends on always-fail.
178s 2025-05-02 03:32:01 Starting service always-fail...
178s 2025-05-02 03:32:01 Service always-fail could not be started.
178s 2025-05-02 03:32:01 Service always-fail failed to start.
178s 2025-05-02 03:32:01 Service fourth depends on always-fail.
178s 2025-05-02 03:32:01 Stopping service root...
178s 2025-05-02 03:32:01 Exiting shepherd...
178s 2025-05-02 03:32:01 Service always-fail is not running.
178s 2025-05-02 03:32:01 Service test is not running.
178s 2025-05-02 03:32:01 Service test-2 is not running.
178s 2025-05-02 03:32:01 Service one-shotty is not running.
178s 2025-05-02 03:32:01 Stopping service c...
178s 2025-05-02 03:32:01 Service c stopped.
178s 2025-05-02 03:32:01 Service c is now stopped.
178s 2025-05-02 03:32:01 Stopping service b...
178s 2025-05-02 03:32:01 Service b stopped.
178s 2025-05-02 03:32:01 Service b is now stopped.
178s 2025-05-02 03:32:01 Stopping service a...
178s 2025-05-02 03:32:01 Service a stopped.
178s 2025-05-02 03:32:01 Service a is now stopped.
178s 2025-05-02 03:32:01 Service b is not running.
178s 2025-05-02 03:32:01 Service c is not running.
178s 2025-05-02 03:32:01 Service first is not running.
178s 2025-05-02 03:32:01 Service second is not running.
178s + rm -f t-socket-3441 t-conf-3441 t-stamp-3441 t-log-3441
178s + test -f t-pid-3441
178s + cat t-pid-3441
178s + kill 3452
178s tests/one-shot.sh: 2: kill: No such process
178s
178s + true
178s + rm -f t-pid-3441
179s autopkgtest [03:32:01]: test tests-one-shot: -----------------------]
179s autopkgtest [03:32:01]: test tests-one-shot: - - - - - - - - - - results - - - - - - - - - -
179s tests-one-shot PASS
179s autopkgtest [03:32:01]: @@@@@@@@@@@@@@@@@@@@ summary
179s herd--help PASS
179s shepherd--help PASS
179s herd--version PASS
179s shepherd--version PASS
179s tests-basic PASS
179s tests-starting-status PASS
179s tests-one-shot PASS
183s nova [W] Using flock in prodstack7-arm64
183s Creating nova instance adt-questing-arm64-shepherd-20250502-032902-juju-7f2275-prod-proposed-migration-environment-21-4e8d2cb7-1dfb-471e-989f-202aae596101 from image adt/ubuntu-questing-arm64-server-20250501.img (UUID 137c3127-57d2-4bf2-a106-d904ad6e43f4)...
183s nova [W] Timed out waiting for b1eeac7e-5980-4f16-971e-b1a50bf5d7d7 to get deleted.