[SERVER-2659] query_yield2 failure Created: 01/Mar/11 Updated: 12/Jul/16 Resolved: 10/Jun/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 2.1.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Tad Marshall |
| Resolution: | Done | Votes: | 0 |
| Labels: | buildbot | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Test : query_yield2.js ... for test.query_yield2 Sun Feb 27 10:09:39 [conn27] query test.query_yield2 reslen:36 nscanned:200 { $where: function () { var x = this.n; for (var i = 0; i < 25000; i++) ... } nreturned:0 2355ms nreturned:0 2375ms return false; } ).itcount() ); 127.0.0.1:32000 Sun Feb 27 10:09:43 uncaught exception: 100 is not greater than 111 : undefined nreturned:0 6449ms |
| Comments |
| Comment by Tad Marshall [ 10/Jun/12 ] |
|
Test timeout has been changed and this failure does not happen in current runs. |
| Comment by Tad Marshall [ 10/Jun/12 ] |
|
Different issue in the same test. |
| Comment by Tad Marshall [ 10/Jun/12 ] |
|
This test has been substantially modified recently, but at some point the timeout comparison was changed from 100 ms to 200 ms, and the test does not show this particular failure in recent runs. Will link to current issues with this test, then resolve this ticket. |
| Comment by Eliot Horowitz (Inactive) [ 02/Mar/11 ] |
|
We should increase the timeout or figure out a better way to test this |
| Comment by Aaron Staple [ 01/Mar/11 ] |
|
Just a note on what seems to be happening
|