From e8fd7c9ed405dd17e252705324a31cc68ac10a9c Mon Sep 17 00:00:00 2001 From: Frantisek Sumsal Date: Wed, 13 Jan 2021 21:42:13 +0100 Subject: ci: introduce a watchdog for the sanitized unit test run --- .github/workflows/ubuntu-unit-tests.sh | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/.github/workflows/ubuntu-unit-tests.sh b/.github/workflows/ubuntu-unit-tests.sh index 532ee7bf78..d48c4b4bfe 100755 --- a/.github/workflows/ubuntu-unit-tests.sh +++ b/.github/workflows/ubuntu-unit-tests.sh @@ -63,6 +63,16 @@ for phase in "${PHASES[@]}"; do export ASAN_OPTIONS=strict_string_checks=1:detect_stack_use_after_return=1:check_initialization_order=1:strict_init_order=1 # Never remove halt_on_error from UBSAN_OPTIONS. See https://github.com/systemd/systemd/commit/2614d83aa06592aedb. export UBSAN_OPTIONS=print_stacktrace=1:print_summary=1:halt_on_error=1 + + # FIXME + # For some strange reason the GH Actions VM stops responding after + # executing first ~150 tests, _unless_ there's something producing + # output (either running `meson test` in verbose mode, or something + # else in background). Despite my efforts so far I haven't been able + # to identify the culprit (since the issue is not reproducible + # during debugging, wonderful), so let's at least keep a workaround + # here to make the builds stable for the time being. + (set +x; while :; do echo -ne "\n[WATCHDOG] $(date)\n"; sleep 30; done) & meson test --timeout-multiplier=3 -C build --print-errorlogs ;; CLEANUP) -- cgit v1.2.1