Details
-
Improvement
-
Status: Done
-
Medium
-
Resolution: Fixed
-
None
-
None
-
None
Description
This behavior was observed in testing of 3.6.7, 3.6.8, and the master branch (3.7.9).
By default audit test helper functions assume that 3 seconds is enough time between activating some event and checking its presence in the audit log. It seems in this specific case (drop database on mmapv1) this timeout should be increased