shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-03-09 12:58:26 +03:00
Code
systemd/test/units/end.sh

18 lines
716 B
Bash
Raw Normal View History

test: verify json format passed through varlink This drops logs of failed unit tests in TEST-02-UNITTESTS from the journal, as the expected logs from test-varlink-idl makes the post script fail. Saving logs in journal is simply noisy, and we will output anyway after qemu or nspawn finished by check_result_{qemu,nspawn}_unittests().
2023-11-27 06:26:07 +09:00
#!/usr/bin/env bash
# SPDX-License-Identifier: LGPL-2.1-or-later
set -eux
set -o pipefail
test: Rework TEST-02-UNITTESTS Currently, A large amount of unit test output is logged directly to the console instead of to the per test log file as any subprocesses executed by a test manager will detect that stderr is not connected to the journal and log directly to /dev/console instead. To solve this issue, let's make sure all tests are connected directly to the journal by running them with systemd-run. We also simplify the entire test script by getting rid of the custom queue and replicating it with xargs instead. By using bash's function export feature, we can make our run_test() function available to the bash subprocess spawned by xargs. Once a test is finished, we read its logs from the journal and put them in the appropriate file if needed.
2024-04-20 21:13:18 +02:00
(! journalctl -q -o short-monotonic --grep "didn't pass validation" | grep -v "test-varlink-idl" >>/failed)
test: verify json format passed through varlink This drops logs of failed unit tests in TEST-02-UNITTESTS from the journal, as the expected logs from test-varlink-idl makes the post script fail. Saving logs in journal is simply noisy, and we will output anyway after qemu or nspawn finished by check_result_{qemu,nspawn}_unittests().
2023-11-27 06:26:07 +09:00
shared/pam-util: fix awkward tense in log message
2024-02-27 18:32:51 +01:00
# Here, the redundant '[ ]' in the pattern is required in order not to match the logged command itself.
(! journalctl -q -o short-monotonic --grep 'Warning: cannot close sd-bus connection[ ].*after fork' >>/failed)
test: check pam warning message
2024-01-21 13:14:15 +09:00
test: check if sd-executor doesn't complain during (de)serializing This was usually caught by "accident" by other tests that parse output of commands executed by sd-executor, so let's have an explicit check for this.
2024-03-28 15:20:22 +01:00
# Check if sd-executor doesn't complain about not being able to (de)serialize stuff
(! journalctl -q -o short-monotonic --grep "[F]ailed to parse serialized line" >>/failed)
(! journalctl -q -o short-monotonic --grep "[F]ailed to (de)?serialize \w+" >>/failed)
Revert "test: Run end.sh when running integration tests with mkosi" It seems this introduced a regression in the CentOS CI; 14:25:58 FAILED TASKS:14:25:58 ------------- 14:25:58 TEST-03-JOBS 14:25:58 TEST-52-HONORFIRSTSHUTDOWN 14:25:58 TEST-63-PATH Revert for now. This reverts commit da3c6fc55363af2163b4d2613c9951bdaea24810.
2024-06-03 14:51:15 +01:00
systemctl poweroff --no-block
test: verify json format passed through varlink This drops logs of failed unit tests in TEST-02-UNITTESTS from the journal, as the expected logs from test-varlink-idl makes the post script fail. Saving logs in journal is simply noisy, and we will output anyway after qemu or nspawn finished by check_result_{qemu,nspawn}_unittests().
2023-11-27 06:26:07 +09:00
exit 0
Copy Permalink