From 72f06d01b555503245b45690ec645d4bfc43c939 Mon Sep 17 00:00:00 2001 From: Brian Behlendorf Date: Mon, 11 Oct 2021 10:49:13 -0700 Subject: [PATCH] ZTS: deadman_sync fix In the CI environment it's possible for events to be slightly delayed resulting in 4, instead of 5, events appearing in the log file. This isn't a problem and should be considered a success to avoid false positive test results. Reviewed-by: George Melikov Signed-off-by: Brian Behlendorf Closes #12625 --- tests/zfs-tests/tests/functional/deadman/deadman_sync.ksh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/zfs-tests/tests/functional/deadman/deadman_sync.ksh b/tests/zfs-tests/tests/functional/deadman/deadman_sync.ksh index b0b03f5d523e..fd6e8c858edd 100755 --- a/tests/zfs-tests/tests/functional/deadman/deadman_sync.ksh +++ b/tests/zfs-tests/tests/functional/deadman/deadman_sync.ksh @@ -80,10 +80,10 @@ else fi log_must zpool events -# Verify at least 5 deadman events were logged. The first after 5 seconds, +# Verify at least 4 deadman events were logged. The first after 5 seconds, # and another each second thereafter until the delay is clearer. events=$(zpool events | grep -c ereport.fs.zfs.deadman) -if [ "$events" -lt 5 ]; then +if [ "$events" -lt 4 ]; then log_fail "Expect >=5 deadman events, $events found" fi