[SERVER-11573] conc_update.js timing out on Windows 64-bit 2008R2+ Created: 05/Nov/13 Updated: 11/Jul/16 Resolved: 20/Dec/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | sam.helman@10gen.com | Assignee: | hari.khalsa@10gen.com |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 64-bit 2008R2+ |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
This has been happening consistently. Here is the first commit where it timed out: Here is the commit directly before the one above. It actually fails in this commit, and then times out in subsequent commits: It also failed in this commit, a few back from the one above. This creates the possibility the test could be flaky: |
| Comments |
| Comment by Githook User [ 14/Nov/13 ] | |
|
Author: {u'username': u'hkhalsa', u'name': u'Hari Khalsa', u'email': u'hkhalsa@10gen.com'}Message: | |
| Comment by Michael O'Brien [ 05/Nov/13 ] | |
|
Looking closer at where the actual slowness is taking place. Compare: The bulk of the logging in these tests is messages like this one:
In the case of the slow test, each of those log lines are about 2-3 seconds apart. |