systemd/test/TEST-23-UNIT-FILE/TEST-23-UNIT-FILE.units/TEST-23-UNIT-FILE-retry-upheld.service

# SPDX-License-Identifier: LGPL-2.1-or-later
[Unit]
Description=Upheld Unit
Requires=TEST-23-UNIT-FILE-retry-fail.service
After=TEST-23-UNIT-FILE-retry-fail.service

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=echo ok
Uphold/StopWhenUnneeded/BindsTo: requeue when job finishes When a unit is upheld and fails, and there are no state changes in the upholder, it will not be retried, which is against what the documentation suggests. Requeue when the job finishes. Same for the other two queues. 2023-04-12 21:37:45 +01:00			`# SPDX-License-Identifier: LGPL-2.1-or-later`
			`[Unit]`
			`Description=Upheld Unit`
test: Rename testsuite-XX units to match test name Having these named differently than the test itself mostly creates unecessary confusion and makes writing logic against the tests harder so let's rename the testsuite-xx units and scripts to just use the test name itself. 2024-05-11 19:17:13 +02:00			`Requires=TEST-23-UNIT-FILE-retry-fail.service`
			`After=TEST-23-UNIT-FILE-retry-fail.service`
Uphold/StopWhenUnneeded/BindsTo: requeue when job finishes When a unit is upheld and fails, and there are no state changes in the upholder, it will not be retried, which is against what the documentation suggests. Requeue when the job finishes. Same for the other two queues. 2023-04-12 21:37:45 +01:00
			`[Service]`
			`Type=oneshot`
			`RemainAfterExit=yes`
tests: use relative paths in ExecStart= and friends We want to retain some of the full paths in order to test more code paths. But the default should be to use the command name only. This makes the tests less visually cluttered. 2024-01-04 15:24:52 +01:00			`ExecStart=echo ok`