On Fri, 14 Jan 2022 14:33:13 GMT, Jim Laskey wrote:
> Tests were fatally failing (windows) on Github actions. Pumping up the memory
> requirements will hopefully alleviate.
Okay - lets see how it goes.
Thanks,
David
-
Marked as reviewed by dholmes (Reviewer).
PR:
On Fri, 14 Jan 2022 14:33:13 GMT, Jim Laskey wrote:
> Tests were fatally failing (windows) on Github actions. Pumping up the memory
> requirements will hopefully alleviate.
The first three tests allocate (3 x ) two 2G arrays. Thinking that 5G is
cutting it close.
-
PR:
On Fri, 14 Jan 2022 14:33:13 GMT, Jim Laskey wrote:
> Tests were fatally failing (windows) on Github actions. Pumping up the memory
> requirements will hopefully alleviate.
I also pointed out that we see the same error message in our CI and the infra
folk assured me that the paging file was
On Fri, 14 Jan 2022 14:33:13 GMT, Jim Laskey wrote:
> Tests were fatally failing (windows) on Github actions. Pumping up the memory
> requirements will hopefully alleviate.
"Perhaps one of the systems used to run GHA has an inconsistently sized page
file" That has been my thought all along.
On Fri, 14 Jan 2022 14:33:13 GMT, Jim Laskey wrote:
> Tests were fatally failing (windows) on Github actions. Pumping up the memory
> requirements will hopefully alleviate.
If the error message:
```OpenJDK 64-Bit Server VM warning: INFO:
os::commit_memory(0x01cfdf61, 10485760, 0)
On Fri, 14 Jan 2022 14:33:13 GMT, Jim Laskey wrote:
> Tests were fatally failing (windows) on Github actions. Pumping up the memory
> requirements will hopefully alleviate.
Looks fine.
-
Marked as reviewed by shade (Reviewer).
PR: https://git.openjdk.java.net/jdk/pull/7086
Tests were fatally failing (windows) on Github actions. Pumping up the memory
requirements will hopefully alleviate.
-
Commit messages:
- Bump up memory requirements.
Changes: https://git.openjdk.java.net/jdk/pull/7086/files
Webrev:
