diff options
| author | Philip Meulengracht <philip.meulengracht@canonical.com> | 2023-07-14 10:13:24 +0200 |
|---|---|---|
| committer | Michael Vogt <michael.vogt@gmail.com> | 2023-07-17 21:15:39 +0200 |
| commit | 0ee6c919fbd55287bf0476d163c011b85bb69572 (patch) | |
| tree | 20d8242937b14977126b5aab6a90f4f97cf09e71 | |
| parent | 5029c4540a83719c697adb8e26c8c8459812fcbf (diff) | |
t/core/snapd-failover: use SIGKILL instead of SIGSEGV
We should avoid triggering of the segmentation fault check
| -rw-r--r-- | tests/core/snapd-failover/task.yaml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/core/snapd-failover/task.yaml b/tests/core/snapd-failover/task.yaml index 62ab0014cb..de566f66eb 100644 --- a/tests/core/snapd-failover/task.yaml +++ b/tests/core/snapd-failover/task.yaml @@ -59,7 +59,7 @@ execute: | echo "Verify that a random signal does not trigger the failure handling" echo "and snapd is just restarted" - systemctl kill --signal=SIGSEGV snapd.service + systemctl kill --signal=SIGKILL snapd.service started_after_rand_sig="$("$TESTSTOOLS"/journal-state get-log -u snapd.failure | grep -c 'Started Failure handling of the snapd snap.' || true)" |