-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
DevProd Correctness
-
200
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
-
None
in
etc/evergreen_yml_components/tasks/resmoke/server_divisions/query/tasks.yml:2602
the product_limits task is defined as not being patchable
"experimental", "blocked_in_query_alias", ] patchable: false commands: - func: "do setup" - func: "run tests"
It was done in SERVER-94511 and it seems that the motivation was to conserve the resources and not to run this task on every patch.
This causes the problem that when this task fails and I want to test the fix, I can't run it on evergreen any more by creating a patch. Instead I have to go to tasks.yml and enable it before the fix, run the patch, and only then disable it again right before merging.
We should consider using aliases to exclude this particular task from the list of what we run on every merge to master branch.
- is related to
-
SERVER-94511 Behavioral regression tests for maximum-size queries
-
- Closed
-