Bug #20006: [Windows] failed to allocate memory (NoMemoryError) - test/ruby/test_ast.rb

• Status: Third Party's Issue
• Assignee: -
• Target version: -
• Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN

[MSP-Greg (Greg L)]

On GitHub Actions, all ruby-loco windows builds are intermittently failing with logs similar to the below:

D:\a\ruby-loco\ruby-loco\ruby-mingw\bin\ruby.exe: failed to allocate memory (NoMemoryError)
D:\a\ruby-loco\ruby-loco\ruby-mingw\bin\ruby.exe: failed to allocate memory (NoMemoryError)
D:\a\ruby-loco\ruby-loco\ruby-mingw\bin\ruby.exe: failed to allocate memory (NoMemoryError)
D:\a\ruby-loco\ruby-loco\ruby-mingw\bin\ruby.exe: failed to allocate memory (NoMemoryError)
/ruby/tool/lib/test/unit/testcase.rb:173:in `rescue in run': failed to allocate memory (NoMemoryError)
< removed /ruby/tool/lib/test/unit/ lines >
running file: /ruby/test/ruby/test_ast.rb

Of course, I cannot reproduce locally. These errors have been happening for several days.

I have not tried to force the test to run single, as it's running parallel currently.

Thanks, Greg

[k0kubun (Takashi Kokubun)]

• Status changed from Open to Third Party's Issue

Given that the MinGW job on ruby/ruby GitHub Actions is running fine, it seems specific to the ruby-loco configuration. Unless it's happening in ruby/ruby/.github/workflows/mingw.yml as well, it should be discussed under the ruby-loco project.