[SERVER-48074] Blacklist read_write_concern_defaults_application.js test from multiversion suites Created: 11/May/20 Updated: 29/Oct/23 Resolved: 01/Jul/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 4.5.1 |
| Fix Version/s: | 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Kevin Pulo |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Steps To Reproduce: | 0. Enable sharding_multiversion suite |
||||||||||||
| Sprint: | Sharding 2020-06-29 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 26 | ||||||||||||
| Description |
|
The test read_write_concern_defaults_application.js fails on any multiversion suite because the _configsvrCreateCollection command was removed. This make this test to fail. The multiversion_incompatible tag can be added like on this test. |
| Comments |
| Comment by Githook User [ 01/Jul/20 ] | |||
|
Author: {'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com', 'username': 'devkev'}Message: | |||
| Comment by Esha Maharishi (Inactive) [ 25/Jun/20 ] | |||
|
kevin.pulo, It'd be worth seeing if read_write_concern_defaults_application.js could use the last_stable_mongos_commands.js pattern to avoid having to be blacklisted from multiversion suites. The idea is last_stable_mongos_commands.js defines commands that were added/removed from mongos and jstests that load it can define test coverage for commands that only show up in listCommands output in one version, like here:
I don't think we have something like this for commands added/removed from mongod, but could add it. It would also be useful to fix
|