Improve unit test for reporter shutdown order

hosom · Jan 15, 2019 · 12f3ab3 · 12f3ab3
1 parent ed1a50e
commit 12f3ab3
Show file tree

Hide file tree

Showing 4 changed files with 9 additions and 5 deletions.
diff --git a/CHANGES b/CHANGES
@@ -1,4 +1,8 @@
 
+2.6-75 | 2019-01-15 10:30:06 -0600
+
+  * GH-213: change type of vector for-loop index to a count (Jon Siwek, Corelight)
+
 2.6-71 | 2019-01-14 16:11:58 -0600
 
   * GH-205: prioritize use of sigaction() over sigset() (Jon Siwek, Corelight)

diff --git a/VERSION b/VERSION
@@ -1 +1 @@
-2.6-71
+2.6-75
diff --git a/testing/btest/Baseline/core.reporter-shutdown-order-errors/out b/testing/btest/Baseline/core.reporter-shutdown-order-errors/out
diff --git a/testing/btest/core/reporter-shutdown-order-errors.bro b/testing/btest/core/reporter-shutdown-order-errors.bro
@@ -1,6 +1,9 @@
 # @TEST-EXEC: touch reporter.log && chmod -w reporter.log
 # @TEST-EXEC: bro %INPUT >out 2>&1
-# @TEST-EXEC: btest-diff out
+
+# Output doesn't really matter, but we just want to know that Bro shutdowns
+# without crashing in such scenarios (reporter log not writable
+# and also reporter errors being emitting during shutdown).
 
 redef Config::config_files += { "./config" };