[SERVER-56383] Feature flag tag is not preventing a test to run on some non required variants Created: 27/Apr/21 Updated: 12/May/21 Resolved: 12/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Robert Guo (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Sprint: | STM 2021-05-17 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 36 | ||||||||||||||||||||
| Story Points: | 1 | ||||||||||||||||||||
| Description |
|
The Shared Library Enterprise RHEL 8.0 (SBE) does not have all the feature flags enabled, and the test drop_collection_sharded.js has the featureFlagShardingFullDDLSupport tag, so it shouldn't have run on that variant, however, it did and failed, because the shard collection is not resilient to stepdowns without that feature flag. |
| Comments |
| Comment by Robert Guo (Inactive) [ 12/May/21 ] |
|
I ended up fixing this as part of |
| Comment by Brooke Miller [ 27/Apr/21 ] |
|
STM will pick up the investigation for BF-20934 to better understand what the solution could be here. |
| Comment by Robert Guo (Inactive) [ 27/Apr/21 ] |
|
marcos.grillo it should be that if you don't specify the --runAllFeatureFlagTests option, tests with feature flag tags would not run. I'll have to look into it a bit more to see why that's apparently not the case only for the SBE builder. Nothing in the build variant configuration stands out to me. |
| Comment by Marcos José Grillo Ramirez [ 27/Apr/21 ] |
|
robert.guo is it possible that the SBE variant need some flag to prevent tests with feature flag tags to be run? |