[SERVER-11035] count10.js failing on some Enterprise MCI builders Created: 04/Oct/13  Updated: 11/Jul/16  Resolved: 04/Oct/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: David Storch
Resolution: Done Votes: 0
Labels: buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-10382 Interrupted count commands don't retu... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

David - I merged your pull request 511 for SERVER-10382 in rev 1819d0083db

Code review: http://codereview.10gen.com/11598025/, reviewer was scotthernandez

As of now (11 PM Sept 3) , I see two builders that have been failing on your new count10.js test since that commit:

enterprise-suse11-64: http://mci.10gen.com/ui/task/mongodb_mongo_master_enterprise_suse11_64_1819d0083db9d71560a886598a245f12704d4403_13_10_03_22_34_12_js_auth_suse11
http://buildlogs.mongodb.org/mci_0.9_enterprise_suse11_64/builds/1059/test/js_auth_0/count10.js

enterprise-ubuntu1204-64: http://mci.10gen.com/ui/task/mongodb_mongo_master_enterprise_ubuntu1204_64_1819d0083db9d71560a886598a245f12704d4403_13_10_03_22_34_12_js_auth_ubuntu1204
log: http://buildlogs.mongodb.org/mci_0.9_enterprise_ubuntu1204_64/builds/1059/test/js_auth_0/count10.js

MongoDB shell version: 2.5.3-pre-
connecting to: 127.0.0.1:27999/test
Authenticating to admin database as admin with mechanism CRAM-MD5 on connection: connection to 127.0.0.1:27999
1
connecting to: 127.0.0.1:27999/test
assert failed
Error: Printing Stack Trace
    at printStackTrace (src/mongo/shell/utils.js:37:15)
    at doassert (src/mongo/shell/assert.js:6:5)
    at assert (src/mongo/shell/assert.js:14:5)
    at /data/mci/git@github.commongodb/mongo.git/master/jstests/count10.js:27:1
2013-10-04T00:10:31.214+0000 assert failed at src/mongo/shell/assert.js:7
failed to load: /data/mci/git@github.commongodb/mongo.git/master/jstests/count10.js



 Comments   
Comment by auto [ 04/Oct/13 ]

Author:

{u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}

Message: SERVER-11035 fix count10.js MCI failures

Signed-off-by: Ian Whalen <ian@mongodb.com>
Branch: master
https://github.com/mongodb/mongo/commit/b297497910d07493c84eab330d2ed4fcd9e34502

Comment by Ian Whalen (Inactive) [ 04/Oct/13 ]

just saw it pass on js_auth here: http://mci.10gen.com/ui/task/mongodb_mongo_master_enterprise_suse11_64_37a7f2f07fddce4e413a56753473a7333da35432_13_10_04_19_01_34_js_auth_suse11

applying patch now.

Comment by Scott Hernandez (Inactive) [ 04/Oct/13 ]

Matt, let's just commit this since David ran it locally on the failing tests and was able to show it worked with spencer help. We can then cancel/delete the mci patch.

Comment by David Storch [ 04/Oct/13 ]

Rewrote the test to use startParallelShell instead so that auth works correctly, and spencer reviewed. MCI patch: http://mci.10gen.com/ui/patch/524f108d3ff1221bb8000002. If things pass this time, the matching pull request is here: https://github.com/mongodb/mongo/pull/514.

Comment by Scott Hernandez (Inactive) [ 04/Oct/13 ]

spencer was helping and last I saw a version in review which should auth in the async callback that should work, but I haven't see the commit/mci-patch run yet.

The issue was that the async thread wasn't auth'd.

Comment by Matt Kangas [ 04/Oct/13 ]

David, your second MCI patch still seems to have failed dur_passthrough.js on Linux 64 due to count10.js

http://mci.10gen.com/ui/patch/524ed7ea3ff12216b7000003
http://mci.10gen.com/ui/task/mongodb_mongo_master_linux_64_1819d0083db9d71560a886598a245f12704d4403_13_10_04_14_59_54_durability_linux_64
http://buildlogs.mongodb.org/mci_0.9_linux_64/builds/1100/test/durability_0/dur_passthrough.js

 *******************************************
         Test : jstests/count10.js ...
2013-10-04 11:50:20 EDT	
 m30200| 2013-10-04T15:50:19.529+0000 [conn1] CMD: drop test.count10
 m30200| 2013-10-04T15:50:19.530+0000 [conn1] build index on: test.count10 properties: { "v" : 1, "key" : { "_id" : 1 }, "ns" : "test.count10", "name" : "_id_" }
 m30200| 2013-10-04T15:50:19.530+0000 [conn1] build index done.  scanned 0 total records. 0 secs
assert failed
Error: Printing Stack Trace
    at printStackTrace (src/mongo/shell/utils.js:37:15)
    at doassert (src/mongo/shell/assert.js:6:5)
    at assert (src/mongo/shell/assert.js:14:5)
    at jstests/count10.js:28:1
    at /data/mci/git@github.commongodb/mongo.git/master/jstests/dur/dur_passthrough.js:35:68

Did you submit a later patch that ran cleanly?

I am out of the office today; please grab Scott to help you if you're not sure how to resolve this. (since he reviewed your request originally)

Comment by David Storch [ 04/Oct/13 ]

Code review at this pull request: https://github.com/mongodb/mongo/pull/513

Comment by David Storch [ 04/Oct/13 ]

After more investigation, the problem is auth related, not timing related. New MCI patch: http://mci.10gen.com/ui/patch/524ed7ea3ff12216b7000003. This should do the trick.

Comment by David Storch [ 04/Oct/13 ]

Hopefully this is just a timing issue when things are running slower on MCI. I pushed a patch to MCI to test: http://mci.10gen.com/ui/patch/524ec7083ff1224029000005

Comment by Eric Milkie [ 04/Oct/13 ]

Buildbot plain jane Linux 64 is failing in dur_passthrough.js due to the same problem. It's not Enterprise specific.

Comment by Matt Kangas [ 04/Oct/13 ]

Other "passthrough" tests that failed on count10.js also:

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