[CDRIVER-894] test_exhaust_cursor fails on new reconnect code Created: 30/Sep/15  Updated: 19/Oct/16  Resolved: 01/Oct/15

Status: Closed
Project: C Driver
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2-rc0

Type: Bug Priority: Major - P3
Reporter: Kyle Suarez Assignee: A. Jesse Jiryu Davis
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Mac OSX


Issue Links:
Related
related to CDRIVER-830 Exhaust cursors must destroy the stre... Closed

 Description   

I am not sure why, but the test hangs when testing the exhaust cursors.

{'kyle@viridian':'~/Programming/mongo-c-driver', 'git':'(detachedfromorigin/1.2.0-dev)'}
$ ./test-libmongoc -f -p -l "/Client/exhaust*"                                                                                                                                                                                                                                
{
  "uri": "mongodb://localhost:27017/",
  "is_mongos": "false",
  "host": {
    "sysname": "Darwin",
    "release": "14.5.0",
    "machine": "x86_64",
    "memory": {
      "pagesize": 4096,
      "npages": 0
    }
  },
  "options": {
    "parallel": "false",
    "fork": "false"
    "tracing": "false"
  },
  "tests": [
cursor error: Failed to read 4 bytes from socket within 300000 milliseconds.
Assertion failed: (r), function test_exhaust_cursor, file tests/test-mongoc-exhaust.c, line 164.
Abort trap: 6

I've noticed this on both a standalone and a single-node replica set.



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

Author:

{u'username': u'bjori', u'name': u'Hannes Magnusson', u'email': u'bjori@php.net'}

Message: CDRIVER-894: Race condition in connecting to node
Branch: 1.2.0-dev
https://github.com/mongodb/mongo-c-driver/commit/6873346f9ca15bfe85d0a095f498b6e3e0e4b196

Comment by Hannes Magnusson [ 30/Sep/15 ]

/Client/authenticate_failure is also failing on OSX with this error message: (after custom patch build adding the actual error message before the failed errorcode assert)

[2015/09/30 07:52:36.683] Error domain: 2, error code: 4, errmsg: Failed to read 4 bytes from socket within 300000 milliseconds.

I can repro that on my laptop, and git bisect blamed it down to

73f04b86dc61afcf8f922c9e46bddeec621f23f4 is the first bad commit
commit 73f04b86dc61afcf8f922c9e46bddeec621f23f4
Author: A. Jesse Jiryu Davis <jesse@mongodb.com>
Date:   Tue Sep 29 10:32:20 2015 -0400
 
    CDRIVER-830 Much simpler reconnects.
 
:040000 040000 7bb05e61ef69fbf153ec059280b20e32baacbdd6 43c591f7ea5f034f514c4afa5cf7f23568419405 M src
:040000 040000 a82ace745eea34de6184c24deb5acaa319c80387 5a36a88feb01667dbfd18631548e6d9f382d6f03 M tests
bisect run success
  224.17s user 101.32s system 74% cpu 7:15.09 total

I can't quite tell what exactly is the problem yet though

Generated at Wed Feb 07 21:10:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.