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
Describe the bug
internal pipeline rapids_integration-dev-github #758#762
the executor failed test cases due to lost executor.
After investigation, we found that the memory usage of testing w/ jdk11 is abnormal, and it exceeded the resource limitation of our test ENV.
all other combinations took around 45~50G memory at most,
but jdk11 one consumed more than 55G and caused the OOM kill, this seems always reproducible
Steps/Code to reproduce bug
Please provide a list of steps or a code sample to reproduce the issue.
Avoid posting private or sensitive data.
Expected behavior
A clear and concise description of what you expected to happen.
Environment details (please complete the following information)
but still failed OOM kill (FYI last night's regular run passed w/ mem footprint peak close to 55GB, but did not reach that)
I am going to limit the test parallelism (currently 6) to 4 in JDK11 nightly IT to unblock downstream tests for now
Describe the bug
internal pipeline rapids_integration-dev-github #758 #762
the executor failed test cases due to lost executor.
After investigation, we found that the memory usage of testing w/ jdk11 is abnormal, and it exceeded the resource limitation of our test ENV.
all other combinations took around 45~50G memory at most,
but jdk11 one consumed more than 55G and caused the OOM kill, this seems always reproducible
Steps/Code to reproduce bug
Please provide a list of steps or a code sample to reproduce the issue.
Avoid posting private or sensitive data.
Expected behavior
A clear and concise description of what you expected to happen.
Environment details (please complete the following information)
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: