summaryrefslogtreecommitdiffstats
path: root/docs/PAX_CONTROL_GROUPS.md
diff options
context:
space:
mode:
authorDaan De Meyer <daan.j.demeyer@gmail.com>2024-04-20 21:13:18 +0200
committerDaan De Meyer <daan.j.demeyer@gmail.com>2024-04-22 19:37:13 +0200
commit741d59b326ea25053097fcbf004864ea6b3c6299 (patch)
tree78a90c24e2241e45b53b8fa42bb65a9fbe2edb2c /docs/PAX_CONTROL_GROUPS.md
parentMerge pull request #32392 from DaanDeMeyer/executor-log-level (diff)
downloadsystemd-741d59b326ea25053097fcbf004864ea6b3c6299.tar.xz
systemd-741d59b326ea25053097fcbf004864ea6b3c6299.zip
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.
Diffstat (limited to 'docs/PAX_CONTROL_GROUPS.md')
0 files changed, 0 insertions, 0 deletions