From 123d2803bfb9b754cee7e721a67a151380efd7e7 Mon Sep 17 00:00:00 2001 From: Brian Behlendorf Date: Tue, 3 Nov 2020 09:19:45 -0800 Subject: ZTS: Wait on all events in events_001_pos.ksh The events_001_pos.ksh test case can fail because it's possible, and correct, for the config_sync event to be posted after the last "expected" event. To accommodate this the run_and_verify() function has been updated to wait for all non-history events, not just the last event. This does not increase the run time of the test as long as all the events do get generated. Reviewed-by: George Melikov Signed-off-by: Brian Behlendorf Closes #11147 --- tests/zfs-tests/tests/functional/events/events_common.kshlib | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) (limited to 'tests/zfs-tests') diff --git a/tests/zfs-tests/tests/functional/events/events_common.kshlib b/tests/zfs-tests/tests/functional/events/events_common.kshlib index 5f4c629dc..9c5879183 100644 --- a/tests/zfs-tests/tests/functional/events/events_common.kshlib +++ b/tests/zfs-tests/tests/functional/events/events_common.kshlib @@ -119,8 +119,16 @@ function run_and_verify # If the only event is history then we don't observe zed debug log if [[ "${events[0]}" != "sysevent.fs.zfs.history_event" ]]; then - # wait for the last event to show up in the debug log - log_must file_wait_event $ZED_DEBUG_LOG ${events[-1]} + # wait for all the non-history events to show up in the + # debug log, all-debug.sh filters history events. + for event in ${events[*]}; do + if [[ "$event" == \ + "sysevent.fs.zfs.history_event" ]]; then + continue + fi + + log_must file_wait_event $ZED_DEBUG_LOG "$event" + done log_must cp $ZED_DEBUG_LOG $TMP_EVENTS_ZED log_must test -s $TMP_EVENTS_ZED -- cgit v1.2.3