Details
-
Bug
-
Resolution: Done
-
Major - P3
-
2.6.0-rc2
-
None
-
ALL
-
0
Description
|
2014-04-02T08:14:10.945-0400 [testsuite] going to run test: JSTests::InvokeLogError
|
2014-04-02T08:14:10.964-0400 [journal] DurParanoid map check 133ms for 192MB
|
2014-04-02T08:14:10.978-0400 [testsuite] FAIL: JSTests::InvokeLogError Expected: !_logger.logged() @src/mongo/dbtests/jstests.cpp:212
|
In test.exe, JSTests::InvokeLogError expects nothing to be written to the log. Unfortunately, the journal thread can randomly wake up and log a message while this test is running, and when this happens, the test fails. The test needs to be rewritten to handle this, or else we need to change the paranoid mode of the journal to not log messages at random times.
Attachments
Issue Links
- related to
-
SERVER-14476 JSTests::invokeLogError log check is still flawed
-
- Closed
-