[SERVER-20799] basicPlus.js failed on Windows 2008R2 DEBUG while running crud_api.js Created: 06/Oct/15  Updated: 15/Oct/15  Resolved: 07/Oct/15

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 3.2.0-rc0

Type: Bug Priority: Major - P3
Reporter: Gabriel Russell (Inactive) Assignee: Max Hirschhorn
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-20730 Automatically detect parallel suite f... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: QuInt A (10/12/15)
Participants:

 Description   

[js_test:basicPlus] 2015-10-06T16:33:11.063+0000 assert: command failed: { "ok" : 0, "errmsg" : "operation exceeded time limit", "code" : 50 } : undefined
[js_test:basicPlus] 2015-10-06T16:33:11.063+0000 _getErrorWithCode@src/mongo/shell/utils.js:23:13
[js_test:basicPlus] 2015-10-06T16:33:11.063+0000 doassert@src/mongo/shell/assert.js:13:14
[js_test:basicPlus] 2015-10-06T16:33:11.063+0000 assert.commandWorked@src/mongo/shell/assert.js:259:5
[js_test:basicPlus] 2015-10-06T16:33:11.063+0000 DBCommandCursor.prototype._runGetMoreCommand@src/mongo/shell/query.js:716:5
[js_test:basicPlus] 2015-10-06T16:33:11.063+0000 DBCommandCursor.prototype._hasNextUsingCommands@src/mongo/shell/query.js:744:9
[js_test:basicPlus] 2015-10-06T16:33:11.063+0000 DBCommandCursor.prototype.hasNext@src/mongo/shell/query.js:752:1
[js_test:basicPlus] 2015-10-06T16:33:11.063+0000 DBQuery.prototype.toArray@src/mongo/shell/query.js:306:13
[js_test:basicPlus] 2015-10-06T16:33:11.065+0000 crudAPISpecTests@jstests/core/crud_api.js:734:22
[js_test:basicPlus] 2015-10-06T16:33:11.065+0000 @jstests/core/crud_api.js:774:5
[js_test:basicPlus] 2015-10-06T16:33:11.065+0000 @jstests/core/crud_api.js:1:2



 Comments   
Comment by Githook User [ 07/Oct/15 ]

Author:

{u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}

Message: SERVER-20799 Remove aggregation + maxTimeMS test case from crud_api.js.

Had caused intermittent failures when run in parallel with other tests.
Branch: master
https://github.com/mongodb/mongo/commit/3d727191a98407c76d48bb9a4c53bd312488b879

Comment by Max Hirschhorn [ 06/Oct/15 ]

The following operation definitely took more than 100 milliseconds. I think we should just fix the test. It doesn't actually confirm that the server received the maxTimeMS and allowDiskUse options.

// Set the maxTimeMS and allowDiskUse on aggregation query
var result = coll.aggregate([{$match: {}}], {batchSize:2, maxTimeMS:100, allowDiskUse:true}).toArray();
assert.eq(2, result.length);

[MongoDFixture:job0] 2015-10-06T16:33:11.057+0000 I COMMAND  [conn90] command test.crud_tests command: aggregate { aggregate: "crud_tests", pipeline: [ { $match: {} } ], maxTimeMS: 100.0, allowDiskUse: true, cursor: { batchSize: 2.0 } } cursorid:21878151994759 ntoreturn:1 ntoskip:0 keyUpdates:0 writeConflicts:0 numYields:0 reslen:200 locks:{ Global: { acquireCount: { r: 6 }, acquireWaitCount: { r: 1 }, timeAcquiringMicros: { r: 1022043 } }, MMAPV1Journal: { acquireCount: { r: 3 } }, Database: { acquireCount: { r: 3 } }, Collection: { acquireCount: { R: 3 } } } protocol:op_command 515ms

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