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

Ignore socket exceptions in initial_sync_unsupported_auth_schema.js test

    • Fully Compatible
    • ALL
    • Sharding 2 04/24/15

      The regression test for SERVER-17671 (initial_sync_unsupported_auth_schema.js) can fail if cluster reinitialization coincides with the new node aborting. The solution is to ignore socket exceptions in addition to the already ignored query errors.

      Patch build failure from a windows-64-2k8-debug host:

      2015-04-10T19:03:32.422+0000 I NETWORK  Socket say send() errno:10054 An existing connection was forcibly closed by the remote host. 127.0.0.1:31002
      2015-04-10T19:03:32.433+0000 E QUERY    Error: socket exception [SEND_ERROR] for 127.0.0.1:31002
          at DBQuery._exec (src/mongo/shell/query.js:102:40)
          at DBQuery.hasNext (src/mongo/shell/query.js:250:10)
          at DBCollection.findOne (src/mongo/shell/collection.js:188:19)
          at DB.runCommand (src/mongo/shell/db.js:58:41)
          at src/mongo/shell/replsettest.js:358:55
          at Function.assert.soon (src/mongo/shell/assert.js:183:17)
          at ReplSetTest.awaitSecondaryNodes (src/mongo/shell/replsettest.js:351:10)
          at ReplSetTest.initiate (src/mongo/shell/replsettest.js:460:10)
          at ReplSetTest.reInitiate (src/mongo/shell/replsettest.js:475:10)
          at testInitialSyncAbortsWithUnsupportedAuthSchema (C:\data\mci\shell\src\jstests\replsets\initial_sync_unsupported_auth_schema.js:24:13)
          at C:\data\mci\shell\src\jstests\replsets\initial_sync_unsupported_auth_schema.js:92:1 at C:\data\mci\shell\src\jstests\replsets\initial_sync_unsupported_auth_schema.js:30
      failed to load: C:\data\mci\shell\src\jstests\replsets\initial_sync_unsupported_auth_schema.js
      

            Assignee:
            kamran.khan Kamran K.
            Reporter:
            kamran.khan Kamran K.
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: