Make TestNodeMemoryConfig success independent of running heap size #23080
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.
Description
There is a mismatch between the default values in
com.facebook.presto.memory.NodeMemoryConfig
, which are a factor of the runtime heap size, and the test override values incom.facebook.presto.memory.TestNodeMemoryConfig
, which are hard-coded. This can cause the tests to fail when: (heap size) * (default factor) == (test override).Motivation and Context
When run with a 5GB heap, tests will fail due to the hard-coded values:
Impact
Test Plan
Contributor checklist
Release Notes