Increase delay for zed log in events tests

In zed event test cases, a brief delay was introduced
to allow for events to make it to the zed log. On at least
one buildbot builder, the 1 second delay is not long enough.
Therefore, increasing the delay should ensure the zed has
more than enough time to write to its log.

Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Giuseppe Di Natale <dinatale2@llnl.gov>
Closes #6395

diff --git a/tests/zfs-tests/tests/functional/events/events_common.kshlib b/tests/zfs-tests/tests/functional/events/events_common.kshlib
index afefef1f0a9853c9e3b7f192dd8c3e2599b1e740..9ef97ca62e9586b6e9b075da249f5562221391d6 100755 (executable)
--- a/tests/zfs-tests/tests/functional/events/events_common.kshlib
+++ b/tests/zfs-tests/tests/functional/events/events_common.kshlib
@@ -68,7 +68,7 @@ function run_and_verify
        log_must zpool events > $TMP_EVENTS 2>/dev/null
        log_must zpool events -v > $TMP_EVENTS_FULL 2>/dev/null
        if [[ -f $zedlog ]]; then
-               sleep 1 # Brief delay for the ZED to handle the event.
+               sleep 5 # Brief delay for the ZED to handle the event.
                diff $zedlog.old $zedlog | grep "^> " | sed 's/^> //g' \
                    >$TMP_EVENTS_ZED
        fi