Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-10837

trace_missing_docs_test.js (sharding) failing on Win 32 bit

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.5.3
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • Labels:
    • Environment:
      Windows 32-bit
      Nightly Windows 32-bit
      Others?
    • Fully Compatible
    • ALL

      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

            Assignee:
            greg_10gen Greg Studer
            Reporter:
            matt.kangas Matt Kangas
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: