systemd/test/TEST-22-TMPFILES/testsuite.service

[Unit]
Description=Testsuite service
After=systemd-tmpfiles-setup.service
Before=getty-pre.target
Wants=getty-pre.target

[Service]
WorkingDirectory=/testsuite
ExecStart=/testsuite/run-tmpfiles-tests.sh
Type=oneshot
StandardOutput=tty
StandardError=tty
test: add tests for systemd-tmpfiles 2018-03-05 14:32:18 +03:00			`[Unit]`
			`Description=Testsuite service`
test: drop 'After=multi-user.target' from most of testsuite.service 2018-11-02 04:27:56 +03:00			`After=systemd-tmpfiles-setup.service`
test: make sure our tests get exclusive TTY access This sould make our test suite a bit more robust if it is slow running. A few of our test services use StandardOutput=tty or StandardError=tty in the tests in order to connect test services to the container console. This gets into conflict with the container getty which wants exclusive access to the console. Since the container getty is started with Type=idle it typically gets started after a timeout only if the TTY is already used, which hence introduces a race: if the test finishes earlier all is good, if not, then the test gets kicked off the TTY which then causes bash to abort since it cannot write any error messages anymore. Let's fix this hence: all tests that connect to the tty are now synchronized to getty-pre.target, so they finish before any getty is started. 2019-11-19 20:54:47 +03:00			`Before=getty-pre.target`
			`Wants=getty-pre.target`
test: add tests for systemd-tmpfiles 2018-03-05 14:32:18 +03:00
			`[Service]`
			`WorkingDirectory=/testsuite`
			`ExecStart=/testsuite/run-tmpfiles-tests.sh`
			`Type=oneshot`
test: make TEST-22 easier to debug, by outputting to /dev/console 2018-08-06 21:57:26 +03:00			`StandardOutput=tty`
			`StandardError=tty`