[SERVER-15036] add logging inside failing test index_retry.js Created: 26/Aug/14 Updated: 08/Sep/14 Resolved: 26/Aug/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 2.7.6 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | David Storch | Assignee: | David Storch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Description |
|
Test index_retry.js is failing intermittently on windows build variants. The likely cause is slow IO. Additional logging in order to determine the rate at which the test's background index build is proceeding is needed in order to confirm. |
| Comments |
| Comment by Githook User [ 26/Aug/14 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: |