You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The above PR was merged today, and helps with making it easier to detect whether a test failed due to an OutOfMemoryException.
By detecting OOMs and adjusting the exit code returned by the test runner to 137, tools can use that information to automatically retry the execution with more memory available. This is especially helpful in the context of remote execution, where the action may be retried on a larger executor.
For this change to take effect, we need a release of both rules_java and java_tools
cc @bazelbuild/triage
The text was updated successfully, but these errors were encountered:
@iancha1992 Please continue with bazelbuild/java_tools#93 but I'll make the final rules_java release. Something needs to be fixed in the workflow first.
Link to relevant issue and/or commit:
bazelbuild/bazel@2df486e (bazelbuild/bazel#24436)
Other details:
The above PR was merged today, and helps with making it easier to detect whether a test failed due to an OutOfMemoryException.
By detecting OOMs and adjusting the exit code returned by the test runner to 137, tools can use that information to automatically retry the execution with more memory available. This is especially helpful in the context of remote execution, where the action may be retried on a larger executor.
For this change to take effect, we need a release of both
rules_java
andjava_tools
cc @bazelbuild/triage
The text was updated successfully, but these errors were encountered: