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

mongos sharding assertion in shard3.js unit test from RHEL build

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding, Testing Infrastructure
    • None
    • Environment:
      RHEL
    • ALL 

       m30998| Sun Feb 12 11:57:18 [conn1] Assertion: 10181:not sharded:test.foo
 m30998| 0x7a8ca6 0x7a926c 0x5cdaeb 0x5cea14 0x568da3 0x4e7e05 0x4d6e0b 0x52d5fc 0x544ec4 0x61f312 0x3088a0673d 0x30882d44bd 
 m30998| Received signal 11

      From line 99 of shard3.js

      http://buildbot.mongodb.org:8081/builders/Nightly%20Linux%20RHEL%2064-bit/builds/3/steps/test_5/logs/stdio
      After the assertion, the unit test did not exit but just hung forever waiting for a mongos that was no longer there

            Assignee:
            greg_10gen Greg Studer
            Reporter:
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: