killop.js test not finding correct number of ops in 2.0 branch

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • Environment:
      V2.0 Linux RHEL 64-bit
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      sh7946| MongoDB shell version: 2.0.5
      sh7948| MongoDB shell version: 2.0.5
      sh7946| connecting to: 127.0.0.1:32000/test
      Wed May  9 07:39:58 [initandlisten] connection accepted from 127.0.0.1:48111 #702
      Wed May  9 07:39:58 [initandlisten] connection accepted from 127.0.0.1:48112 #703
      sh7948| connecting to: 127.0.0.1:32000/test
      Wed May  9 07:40:15 [clientcursormon] mem (MB) res:271 virt:4067 mapped:1856
      assert.soon failed: function () {
          o = ops();
          return o.length == 2;
      }, msg:undefined
      Error("Printing Stack Trace")@:0
      ()@shell/utils.js:35
      ("assert.soon failed: function () {\n    o = ops();\n    return o.length == 2;\n}, msg:undefined")@shell/utils.js:46
      ((function () {o = ops();return o.length == 2;}))@shell/utils.js:150
      @/data/buildslaves/Linux_RHEL_64bit_V2.0/mongo/jstests/killop.js:30
      

      http://buildbot.mongodb.org/builders/V2.0%20Linux%20RHEL%2064-bit/builds/100/steps/test_1/logs/stdio

            Assignee:
            Andy Schwerin
            Reporter:
            Ian Whalen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: