Ensure multiJVM set to plain Yes for jck17+ Windows #4506
Conversation
Signed-off-by: Andrew Leonard <[email protected]>
|
Grinder run on x64 Linux (uses multiJVM group) : https://ci.eclipse.org/temurin-compliance/job/Grinder/3293/ |
There was a problem hiding this comment.
Everyone using these files picks up this change (where before they had the ability to set things in their copy of default config files). I am approving, but ideally we sequester such changes to vendor default config so as not to force a change on others if they did not need it (like if they have beefier Windows machines).
There was a problem hiding this comment.
Agree with Shelley's comment - we should revisit this post release to diagnose and attempt to test with this option enabled across environments (I'll also note that we switched it to multiJVM_group without too much discussion with external parties to my knowledge)
MultiJVM=group option for jck17+ causes memory exhaustion on Windows platform, so ensure for multiJVM execution type that MultiJVM is set to just "Yes"
Works around issue: #4502 (comment)