Use 12g for BSD VM memory in GHA - #70
Merged
Merged
Conversation
snake66
approved these changes
Jul 30, 2026
snake66
left a comment
snake66
left a comment
Collaborator
There was a problem hiding this comment.
Nice find! Change looks good!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I noticed that some of the intermittent failures on OpenBSD testing in GHA appeared to be with tests that use a large amount of memory, such as
java/math/BigInteger/largeMemory/SymmetricRangeTests.java. With OpenBSD's heavy use of address space layout randomization, I surmised that perhaps a lack of physical memory in the guest OS may be the cause.Increasing the guest OS memory from 11g to 12g does appear to eliminate the intermittent failure I occasionally see on OpenBSD in GHA with
SymmetricRangeTests.java. I ran 10 GHA with this change and the only remaining intermittent failure I see now is underjdk/jshell/*which I believe to be unrelated at this time.