test/test.service.in

# SPDX-License-Identifier: LGPL-2.1-or-later
[Unit]
Description=%N
Wants=basic.target network.target @wants@
After=basic.target network.target @after@
@unit@

[Service]
ExecStartPre=rm -f /failed /testok
ExecStart=@command@
ExecStartPost=/usr/lib/systemd/tests/testdata/units/post.sh
Type=oneshot
MemoryAccounting=@memory-accounting@
Environment=SYSTEMD_PAGER= @env@
UnsetEnvironment=JOURNAL_STREAM
@service@
test: Generate basic testsuite services with meson Most of these are identical, let's just generate from a meson template. 2024-05-12 10:50:47 +02:00			`# SPDX-License-Identifier: LGPL-2.1-or-later`
			`[Unit]`
			`Description=%N`
test: optionally allow to disable user service manager, and disable it on TEST-64 The test triggers many uevents, and running both system and user service managers make the test slow. 2024-05-31 16:29:00 +09:00			`Wants=basic.target network.target @wants@`
			`After=basic.target network.target @after@`
test: Use test.service template for all integration tests Instead of having some tests have their own unit, let's make test.service.in generic enough so that it works for all integration tests. 2025-04-02 21:58:59 +02:00			`@unit@`
test: Generate basic testsuite services with meson Most of these are identical, let's just generate from a meson template. 2024-05-12 10:50:47 +02:00
			`[Service]`
			`ExecStartPre=rm -f /failed /testok`
			`ExecStart=@command@`
test: re-enable journal checks for varlink-idl and so on Previously, we have checked journal after TEST-XX-YYYYY.sh, but it was forgotten when we switched to mkosi. This re-enable the check but through ExecStartPost=, and drops unnecessary workarounds for end.service. Then, this drops unnecessary end.service and testsuite.target. 2025-09-04 06:01:52 +09:00			`ExecStartPost=/usr/lib/systemd/tests/testdata/units/post.sh`
test: Generate basic testsuite services with meson Most of these are identical, let's just generate from a meson template. 2024-05-12 10:50:47 +02:00			`Type=oneshot`
			`MemoryAccounting=@memory-accounting@`
test: Make it possible to run the integration tests standalone Currently, to run the integration tests, it's still necessary to install various other build tools besides meson: A compiler, gperf, libcap, ... which we want to avoid in CI systems where we receive prebuilt systemd packages and only want to test them. Examples are Debian's autopkgtest CI and Fedora CI. Let's make it possible for these systems to run the integration tests without having to install any other build dependency besides meson by extracting the logic required to run the integration tests with meson into a separate subdirectory and adding a standalone top-level meson.build file which can be used to configure a meson tree with as its only purpose running the integration tests. Practically, we do the following: - all the integration test directories and integration-test-wrapper.py are moved from test/ to test/integration-test/. - All the installation logic is kept out of test/integration-test/ or any of its subdirectories and moved into test/meson.build instead. - We add test/integration-test/standalone/meson.build to run the integration tests standalone. This meson file includes test/integration-test via a cute symlink hack to trick meson into including a parent directory with subdir(). - Documentation is included on how to use the new standalone mode. - TEST-64-UDEV-STORAGE and TEST-85-NETWORK are changed to generate separate units for each testcase to make them behave more like the other integration tests. 2025-03-26 14:30:20 +01:00			`Environment=SYSTEMD_PAGER= @env@`
test: Unset JOURNAL_STREAM for integration test units We use StandardOutput=journal+console for integration test units to make sure the output from the test ends up on both the serial console and in the journal. Unfortunately this only works for messages written to stdout/stderr of the test service. All journal messages logged by systemd tools will only end up in the journal and not on the serial console. This makes test failures harder to debug than needed because developers have to fetch the journal to figure out the actual error that was logged by any systemd tool that failed when invoked from the integration test script. To fix this, let's unset $JOURNAL_STREAM for the integration test units. This forces all output to go through stdout, which will make journald forward it to the console and save it in the journal. 2025-04-02 20:43:41 +02:00			`UnsetEnvironment=JOURNAL_STREAM`
test: Use test.service template for all integration tests Instead of having some tests have their own unit, let's make test.service.in generic enough so that it works for all integration tests. 2025-04-02 21:58:59 +02:00			`@service@`