[SERVER-18263] apply_ops1.js fails if run alone against a master slave deployment. Created: 29/Apr/15 Updated: 02/Aug/18 Resolved: 11/May/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Testing Infrastructure |
| Affects Version/s: | 3.1.2 |
| Fix Version/s: | 3.1.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Description |
|
apply_ops1.js succeeds if it is run as part of the larger suite, but not if it is the only test run. This seems to be because the test database undergoes an initial sync during the test, causing the ops to be applied twice. Logs are attached. |
| Comments |
| Comment by Charlie Swanson [ 11/May/15 ] |
|
Fixed with this commit: https://github.com/mongodb/mongo/commit/56dc3a299a7729dc757630cd63f83b7bf20ea9a9 |