debian-forge-composer/test/cases
Ondřej Budai bc1a7dc30c tests: fix journalctl killing once again
3a8c6c8a introduced a new logic for killing journalctl. Unfortunately, it
doesn't work properly. In ostree tests, multiple journalctls are spawned
but there can be only one trap active at a time. This caused all but the last
journalctls to hang indefinitely. Unfortunately, hanging background processes
is something that causes the GitLab CI to hang indefinitely as well.

This commit modifies the logic a bit: The trap is still set. However, there's
also an explicit kill of journalctl after the compose is finished. After the
process is successfully killed, the trap is removed.

Signed-off-by: Ondřej Budai <ondrej@budai.cz>
2021-06-10 07:40:36 +02:00
..
api.sh cloudapi: Add x-rh-identity header filter 2021-06-05 14:47:38 +01:00
aws.sh tests: fix journalctl killing once again 2021-06-10 07:40:36 +02:00
azure.sh tests: fix journalctl killing once again 2021-06-10 07:40:36 +02:00
base_tests.sh base_tests.sh: make the test self-contained 2020-11-10 10:44:13 +00:00
image_tests.sh tests: modify DISTRO_CODE usage 2021-05-12 15:38:30 +03:00
koji.sh tests: move some integration tests to gitlab CI 2021-05-12 15:38:30 +03:00
libvirt.sh test/libvirt: don't test vhd images 2021-05-17 14:55:50 +02:00
ostree-ng.sh tests: fix journalctl killing once again 2021-06-10 07:40:36 +02:00
ostree.sh tests: fix journalctl killing once again 2021-06-10 07:40:36 +02:00
regression-include-excluded-packages.sh test/cases: Introduce common "regression" test for all distros 2021-05-20 13:07:07 +03:00
regression.sh test/cases: Introduce common "regression" test for all distros 2021-05-20 13:07:07 +03:00
vmware.sh tests: fix journalctl killing once again 2021-06-10 07:40:36 +02:00