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 <mail@gmelikov.ru>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Closes #12625
This commit is contained in:
Brian Behlendorf 2021-10-11 10:49:13 -07:00 committed by GitHub
parent a5b464263b
commit 72f06d01b5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions

View File

@ -80,10 +80,10 @@ else
fi fi
log_must zpool events 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. # and another each second thereafter until the delay is clearer.
events=$(zpool events | grep -c ereport.fs.zfs.deadman) 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" log_fail "Expect >=5 deadman events, $events found"
fi fi