[ML] Functional tests - fix job validation API test with maxModelMemoryLimit #68501
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes the job validation API integration test for the scenario that the test environment has
xpack.ml.max_model_memory_limit
set.Details
In the usual test environment (functional test server on local or CI),
xpack.ml.max_model_memory_limit
is not set and the tests are running fine. But on Cloud, this is set and as a result thehalf_estimated_mml_greater_than_mml
bit of the validation response contains an addition (unexpected) keymaxModelMemoryLimit
which makes the tests fail. Since existance and value of this key can not be predicted reliably, it is removed from the validation.