[SERVER-22151] Blacklist lagged_config_secondary.js and similar tests from the sharding_csrs_continuous_config_stepdown_WT suite Created: 12/Jan/16 Updated: 23/Nov/16 Resolved: 12/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.5, 3.3.2 |
| Type: | Task | Priority: | Trivial - P5 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | test-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Completed: | |||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
lagged_config_secondary.js manipulates the config servers already, so it should not be run in the sharding_csrs_continuous_config_stepdown_WT suite that further manipulates them: config server step downs undermine the test. Blacklist any similar tests found. |
| Comments |
| Comment by Githook User [ 30/Mar/16 ] |
|
Author: {u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}Message: Enabling CSRS continuous config stepdown workload in evergreen Patches:
Conflicts: |
| Comment by Githook User [ 12/Jan/16 ] |
|
Author: {u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}Message: |
| Comment by Githook User [ 12/Jan/16 ] |
|
Author: {u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}Message: |