[SERVER-35053] causal consistency passthroughs erroneously blacklist tests Created: 17/May/18 Updated: 29/Oct/23 Resolved: 02/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Xiangyu Yao (Inactive) | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding 2018-07-16 |
| Participants: |
| Description |
|
In causally_consistent_jscore_passthrough.yml, a section does not make sense since we don't inject any read/write concern in the suite. We should probably update the blacklist.
|
| Comments |
| Comment by Githook User [ 02/Jul/18 ] |
|
Author: {'username': 'jsmulrow', 'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com'}Message: |
| Comment by Misha Tyulenev [ 11/Jun/18 ] |
|
causally_consistent_jscore_passthrough.yml does not inject read/writeConcern “majority” but this section is excluding tests that cannot work with “majority” writeConcern |