[SERVER-53886] jstestfuzz (mutational) fuzzer is forcing latest FCV during validate in multiversion tests Created: 19/Jan/21 Updated: 29/Oct/23 Resolved: 27/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Mikhail Shchatko |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | tig-multiversion | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Backport Requested: |
v5.0
|
||||||||||||||||||||
| Sprint: | STM 2021-08-23, STM 2021-09-06, STM 2021-11-01 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 47 | ||||||||||||||||||||
| Story Points: | 2 | ||||||||||||||||||||
| Description |
|
The jstestfuzz*.yml changes in |
| Comments |
| Comment by Githook User [ 27/Oct/21 ] | ||||||||||||||||||||
|
Author: {'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com', 'username': 'MikhailShchatko'}Message: | ||||||||||||||||||||
| Comment by Robert Guo (Inactive) [ 22/Sep/21 ] | ||||||||||||||||||||
|
Going to have to bump this out again. We still need to wait on | ||||||||||||||||||||
| Comment by Robert Guo (Inactive) [ 28/Jun/21 ] | ||||||||||||||||||||
|
There seems to be some errors in the multiversion task generation logic for fuzzers. I didn't look into it further since this code will largely be rewritten in I'm going to commit the change on the jstestfuzz side and mark this ticket as dependent on
| ||||||||||||||||||||
| Comment by Robert Guo (Inactive) [ 16/Jun/21 ] | ||||||||||||||||||||
|
Yeah good point Max. Thanks for the suggestion.
For the impl: we can use the overrides introduced in | ||||||||||||||||||||
| Comment by Max Hirschhorn [ 17/May/21 ] | ||||||||||||||||||||
|
I could be missing something but I wouldn't expect the mutational (jstestfuzz) fuzzer to be able to change the feature compatibility version in the jstestfuzz_*_multiversion tasks without causing secondaries to crash.
Perhaps this ticket is really about preventing the mutational (jstestfuzz) fuzzer from running the setFeatureCompatibilityVersion command based around a TestData option only set in the jstestfuzz_*_multiversion tasks? If the fuzzer isn't capable of running the setFeatureCompatibilityVersion command, then there won't be any need to restore the feature compatibility version to a specific value during collection validation. | ||||||||||||||||||||
| Comment by Brooke Miller [ 26/Jan/21 ] | ||||||||||||||||||||
|
In triaging, robert.guo mentioned that we'll need to figure out how to override the FCV value for multiversion suites. There are a few places to set various flags, but it's difficult to determine where to grab the final value from. (More details to come in the design for the Multiversion project.) |