[SERVER-5803] killop.js test not finding correct number of ops in 2.0 branch Created: 09/May/12  Updated: 25/Jul/13  Resolved: 14/May/12

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Ian Whalen (Inactive) Assignee: Andy Schwerin
Resolution: Won't Fix Votes: 0
Labels: buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

V2.0 Linux RHEL 64-bit


Operating System: ALL
Participants:

 Description   

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



 Comments   
Comment by Andy Schwerin [ 14/May/12 ]

I believe we're not backporting the fix.

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