[SERVER-45139] Blacklist write_result.js from multiversion testing Created: 13/Dec/19 Updated: 29/Oct/23 Resolved: 16/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 4.3 Required |
| Fix Version/s: | 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jason Chan | Assignee: | Jason Chan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Repl 2019-12-16 | ||||
| Participants: | |||||
| Linked BF Score: | 48 | ||||
| Description |
|
Currently, sharding_jscore_passthrough runs sharded clusters as standalone shards by default. As a result, write_result.js also expects the same. Since this test is only run against sharded clusters with standalone shards, we can expect replSet to only be true if it is communicating with the replica set directly. Therefore, this test fails on multiversion tests that run against sharded clusters with replica set shards. After |
| Comments |
| Comment by Githook User [ 16/Dec/19 ] |
|
Author: {'name': 'Jason Chan', 'email': 'jason.chan@mongodb.com', 'username': 'jasonjhchan'}Message: |