[SERVER-10837] trace_missing_docs_test.js (sharding) failing on Win 32 bit Created: 20/Sep/13  Updated: 11/Jul/16  Resolved: 26/Sep/13

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 2.5.3

Type: Bug Priority: Major - P3
Reporter: Matt Kangas Assignee: Greg Studer
Resolution: Done Votes: 0
Labels: buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 32-bit
Nightly Windows 32-bit
Others?


Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

On many recent "Failed mongostest_smokesharding" instances, trace_missing_docs_test.js is the culprit.

	assert: [4] != [5] are not equal : undefined
	Error: Printing Stack Trace
	    at printStackTrace (src/mongo/shell/utils.js:37:15)
	    at doassert (src/mongo/shell/assert.js:6:5)
	    at Function.assert.eq (src/mongo/shell/assert.js:32:5)
	    at testDocMissing (D:\slave\Windows_32bit\mongo\jstests\sharding\trace_missing_docs_test.js:39:8)
	    at D:\slave\Windows_32bit\mongo\jstests\sharding\trace_missing_docs_test.js:47:1
	2013-09-03T20:27:59.912+0000 [4] != [5] are not equal : undefined at src/mongo/shell/assert.js:7
	failed to load: D:\slave\Windows_32bit\mongo\jstests\sharding\trace_missing_docs_test.js

Nightly Windows 32-bit

The first occurrence I can find on the Nightly build is Sept 1 (rev 804f5dbe1f76).

Note, last ticket re: trace_missing_docs_test.js was SERVER-10639



 Comments   
Comment by auto [ 21/Sep/13 ]

Author:

{u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-10837 buildbot trace_missing_docs.js wait for delete to ensure oplog entries
Branch: master
https://github.com/mongodb/mongo/commit/ca1fa9d82a3b180f623774f86ab4ee3a8a43b6e3

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