test: don't flush debug logs to the console

Let's keep the debug logs in the journal, while logging only testsute-*.sh stdout/stderr to the console (ba7abf7). This should make the test output log a bit more readable and potentially the tests itself a bit faster by avoiding console oversaturation. Also, it should significantly reduce the size of artifacts kept by CIs.
2022-06-17 15:06:59 +02:00
parent 94850fb956
commit c84d1c9822
17 changed files with 0 additions and 17 deletions
@@ -4,7 +4,6 @@ set -eux
 set -o pipefail

 systemd-analyze log-level debug
-systemd-analyze log-target console

 test "$(systemctl show -P MainPID testsuite-20.service)" -eq $$

@@ -4,7 +4,6 @@ set -eux
 set -o pipefail

 systemd-analyze log-level debug
-systemd-analyze log-target console

 # Create a binary for which execve() will fail
 touch /tmp/brokenbinary
@@ -4,7 +4,6 @@ set -eux
 set -o pipefail

 systemd-analyze log-level debug
-systemd-analyze log-target console

 systemd-run --wait --unit=test27-one \
            -p StandardOutput=file:/tmp/stdout \
@@ -4,7 +4,6 @@ set -eux
 set -o pipefail

 systemd-analyze log-level debug
-systemd-analyze log-target console

 systemctl disable --now systemd-timesyncd.service

@@ -11,7 +11,6 @@ set -o pipefail

 if test -f /sys/fs/cgroup/system.slice/testsuite-32.service/memory.oom.group; then
    systemd-analyze log-level debug
-    systemd-analyze log-target console

    # Run a service that is guaranteed to be the first candidate for OOM killing
    systemd-run --unit=oomtest.service \
@@ -4,7 +4,6 @@ set -eux
 set -o pipefail

 systemd-analyze log-level debug
-systemd-analyze log-target console

 function test_directory() {
    local directory="$1"
@@ -5,7 +5,6 @@ set -eux
 set -o pipefail

 systemd-analyze log-level debug
-systemd-analyze log-target console

 unit=testsuite-38-sleep.service

@@ -4,7 +4,6 @@ set -eux
 set -o pipefail

 systemd-analyze log-level debug
-systemd-analyze log-target console

 export SYSTEMD_PAGER=
 SERVICE_PATH="$(mktemp /etc/systemd/system/execreloadXXX.service)"
@@ -4,7 +4,6 @@ set -eux
 set -o pipefail

 systemd-analyze log-level debug
-systemd-analyze log-target console

 declare -A property

@@ -7,7 +7,6 @@ set -o pipefail
 MAX_SECS=60

 systemd-analyze log-level debug
-systemd-analyze log-target console

 # test one: Restart=on-failure should restart the service
 systemd-run --unit=one -p Type=oneshot -p Restart=on-failure /bin/bash -c "exit 1" \
@@ -34,7 +34,6 @@ wait_for_state() {
 }

 systemd-analyze log-level debug
-systemd-analyze log-target console
 systemctl service-log-level systemd-homed debug

 # Create a tmpfs to use as backing store for the home dir. That way we can enforce a size limit nicely.
@@ -4,7 +4,6 @@ set -eux
 set -o pipefail

 systemd-analyze log-level debug
-systemd-analyze log-target console

 systemctl start testsuite-47-repro
 sleep 4
@@ -4,7 +4,6 @@ set -ex
 set -o pipefail

 systemd-analyze log-level debug
-systemd-analyze log-target console

 systemctl enable test-honor-first-shutdown.service
 systemctl start test-honor-first-shutdown.service
@@ -4,7 +4,6 @@ set -eux
 set -o pipefail

 systemd-analyze log-level debug
-systemd-analyze log-target console

 # Loose checks to ensure the environment has the necessary features for systemd-oomd
 [[ -e /proc/pressure ]] || echo "no PSI" >>/skipped
@@ -28,7 +28,6 @@ wait_on_state_or_fail () {
 }

 systemd-analyze log-level debug
-systemd-analyze log-target console


 cat >/run/systemd/system/testservice-fail-59.service <<EOF
@@ -5,7 +5,6 @@ set -o pipefail

 setup() {
    systemd-analyze log-level debug
-    systemd-analyze log-target console

    for i in {0..3};
    do
@@ -6,7 +6,6 @@ set -o pipefail
 RESULTS_FILE=/tmp/testsuite66serviceresults

 systemd-analyze log-level debug
-systemd-analyze log-target console

 systemctl start testsuite-66-deviceisolation.service