[SERVER-13460] JSTests::invokeLogError log check is flawed Created: 02/Apr/14  Updated: 04/Sep/14  Resolved: 05/Jun/14

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: 2.6.0-rc2
Fix Version/s: 2.7.2

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Benety Goh
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-14476 JSTests::invokeLogError log check is ... Closed
Operating System: ALL
Participants:
Linked BF Score: 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.



 Comments   
Comment by Githook User [ 05/Jun/14 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-13460 disable DurParanoid during JS scripting engine logging tests
Branch: master
https://github.com/mongodb/mongo/commit/adcf6601f49b8afbe5b0c2b23d0f83ceeeca1fa1

Generated at Thu Feb 08 03:31:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.