From 2446bf172c85f80c0eee8584e9fc97a68c9ed821 Mon Sep 17 00:00:00 2001 From: Stefan Pfaffel Date: Sat, 4 Jan 2025 14:24:45 +0100 Subject: [PATCH] tests: rename files --- .../configuration/enforce-on-log-match-with-error.sh | 7 +++---- test-e2e/configuration/enforce-on-log-match-with-kill.sh | 9 +++++---- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/test-e2e/configuration/enforce-on-log-match-with-error.sh b/test-e2e/configuration/enforce-on-log-match-with-error.sh index 195a646..f525425 100755 --- a/test-e2e/configuration/enforce-on-log-match-with-error.sh +++ b/test-e2e/configuration/enforce-on-log-match-with-error.sh @@ -9,12 +9,11 @@ $main_path run \ --allow-file-system-read \ --no-enforce-on-startup \ --trigger-enforce-on-log-match="enforce gatekeeping" \ ---on-syscall-denied=kill \ +--on-syscall-denied=error \ bash -c $script_path/log-match.bash -# https://specificlanguages.com/posts/2022-07/14-exit-code-137/ -# Exit code 137 is Linux-specific and means that your process was killed by a signal, namely SIGKILL. -# The main reason for a process getting killed by SIGKILL on Linux (unless you do it yourself) is running out of memory.1 +# This is the list of exit codes for wget: +# 4 Network failure if [[ $? -ne 4 && $? -ne 159 ]]; then exit 1 diff --git a/test-e2e/configuration/enforce-on-log-match-with-kill.sh b/test-e2e/configuration/enforce-on-log-match-with-kill.sh index 921620f..bd18378 100755 --- a/test-e2e/configuration/enforce-on-log-match-with-kill.sh +++ b/test-e2e/configuration/enforce-on-log-match-with-kill.sh @@ -9,13 +9,14 @@ $main_path run \ --allow-file-system-read \ --no-enforce-on-startup \ --trigger-enforce-on-log-match="enforce gatekeeping" \ ---on-syscall-denied=error \ +--on-syscall-denied=kill \ bash -c $script_path/log-match.bash -# This is the list of exit codes for wget: -# 4 Network failure +# https://specificlanguages.com/posts/2022-07/14-exit-code-137/ +# Exit code 137 is Linux-specific and means that your process was killed by a signal, namely SIGKILL. +# The main reason for a process getting killed by SIGKILL on Linux (unless you do it yourself) is running out of memory.1 -if [[ $? -ne 4 ]] || [[ $? -eq 159 ]]; then +if [[ $? -ne 137 ]]; then exit 1 fi