[SERVER-12896] Multiversion mongodump/mongorestore tests fail on Windows Created: 25/Feb/14  Updated: 11/Jul/16  Resolved: 26/Feb/14

Status: Closed
Project: Core Server
Component/s: Tools
Affects Version/s: 2.6.0-rc0
Fix Version/s: 2.6.0-rc1

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File dumprestore_24_output.log    
Issue Links:
Related
Operating System: Windows
Participants:

 Description   

The following test combination fails on Windows:

Running multiversion mongodump mongorestore test:

{
"restoreType" : "direct",
"dumpType" : "direct",
"testDbpath" : "D:\\data
db/jstests_tool_dumprestore_24_dbpath_external/",
"dumpDir" : "D:\\data
db/jstests_tool_dumprestore_24_dump_external/",
"mongoRestoreVersion" : "latest",
"mongoDumpVersion" : "latest",
"serverDestVersion" : "latest",
"serverSourceVersion" : "2.4"
}

The failure is:

assert.soon failed: destColl.findOne(), msg:no data after sleep

Error: assert.soon failed: destColl.findOne(), msg:no data after sleep
at Error (<anonymous>)
at doassert (src/mongo/shell/assert.js:11:14)
at Function.assert.soon (src/mongo/shell/assert.js:180:60)
at multiVersionDumpRestoreTest (D:\workspace\mongo\jstests\multiVersion\dumprestore_24.js:146:12)
at D:\workspace\mongo\jstests\multiVersion\dumprestore_24.js:231:5

2014-02-25T16:33:19.241-0500 Error: assert.soon failed: destColl.findOne(), msg:no data after sleep at src/mongo/shell/assert.js:13



 Comments   
Comment by Githook User [ 26/Feb/14 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-12896 MongoRunner fixes to make multiversion tests run on Windows

The system programs either come versioned in the form of
<utility>-<major.minor> (e.g., mongorestore-2.4) or just <utility>. If
change_extension is called on this string, it will replace the minor
version component and the binary will not be found.

In pre-2.6.0rc0 versions, we did not have the server shutdown event and
the stop commands needs to use the old method of connecting on the admin
port and invoking shutdown.
Branch: master
https://github.com/mongodb/mongo/commit/32b36216dd85697c614c4873021387658d31e1a0

Comment by Eric Milkie [ 25/Feb/14 ]

You can also try mixing the platforms (Windows only for 2.4, or only for 2.6) to see which combo fails, to narrow down the issue.

Comment by Kaloian Manassiev [ 25/Feb/14 ]

Passes on Linux and MacOS. I am trying to run it manually on Windows now to see exactly on which stop it fails.

Comment by Eric Milkie [ 25/Feb/14 ]

Does the same test pass on Linux?

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