-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Optimization
(Ticket based on a Slack thread.)
I've consistently gotten system failures for version_burn_in_gen on a series of (what I think) as simple JS test changes:
1 2 3 4 5 6 7 8.
In questioning my sanity, I also ran a patch against the base commit, which completes without error.
Eventually, I landed on this diff as being a minimal reproduction of the system failure... but for the life of me, I can't figure out why. That this patch and this other patch both pass version_burn_in_gen adds to my suspicion that the change to jstests/libs/optimizer_utils.js is the culprit
Does anyone have insight into this? This seems like a pretty big nuisance at minimum, a potentially serious bug at worst.
- is related to
-
SERVER-82200 burn_in_tags should include indirectly affected tests
- Closed