-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
Execution Team 2024-10-14
-
0
Both of these tests depend on certain messages being logged. Testing for the presence of certain log messages has made these tests occasionally flaky (the test would miss the log line, only for the log line to still be printed after), and in general we might not want to be testing for particular logs - this ticket would instead modify these tests to check that the scenarios they test (inserting into a collection with a corrupted .wt file, etc) crash the server with the expected exit code (the abrupt exit code, which is the code that the server crashes with when encountering a
color: Color value is invalid
LOGV2_FATAL_NOTRACE.