Java LS builds fail randomly with error code 137(SIGKILL received?)
See original GitHub issueSee https://ci.eclipse.org/ls/job/jdt-ls-pr/3566/
Caused by: org.apache.maven.plugin.MojoFailureException: An unexpected error occurred while launching the test runtime (process returned error code 137(SIGKILL received?)).
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Exit code 137 - Specific Languages
Exit code 137 is Linux-specific and means that your process was killed by a signal, namely SIGKILL . The main reason for a...
Read more >Why are my Gradle builds dying with exit-code 137?
If this occurs on Linux you may see builds terminate with exit code 137 (128 + signal number for SIGKILL). The dmesg command...
Read more >Container crashes with code 137 when given high load #22211
Exit code 137 means your process was sent a SIGKILL. ... Setting a memory-limit only prevents the kernel from randomly killing other processes...
Read more >Bug listing with status RESOLVED with resolution FIXED as at ...
status :RESOLVED resolution:FIXED severity:normal ... Bug:155 - "php fails to compile due to java problems" status:RESOLVED resolution:FIXED severity:normal ...
Read more >Developer Guide OpenShift Container Platform 3.11
OpenShift Pipeline Builds" Collapse section "7.5. ... The "application" today is more than just the source code written in Java, Perl, Python, etc....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

It isn’t used. I have removed it from jdt-ls-pr and jdt.ls-master
Nice. I see we went with similar arguments to what are used in vscode-java, which is probably the right approach.
Do you know what requires
java9.home? I couldn’t find it referenced anywhere in JDT-LS. I seejava8fx.homefor a test but nothing else.