-
Type: Bug
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
ALL
-
Execution Team 2021-06-14
In invalid_index_spec.js and initial_sync_invalid_index_spec.js, we verify whether a log message is present using
assert(rawMongoProgramOutput().search(/regex/));
However, the search() function returns the index of the first match, or -1 if there was no match. Thus, the current usage does not properly assert that the log message is present. These should be changed to either
assert.neq(rawMongoProgramOutput().search(/regex/), -1);
assert(/regex/.test(rawMongoProgramOutput());
- related to
-
SERVER-49302 Properly assert that expected log messages are present in hybrid_unique_index_with_updates.js
- Closed
-
SERVER-46026 Fix tests reliant on specific log lines
- Closed