-
Notifications
You must be signed in to change notification settings - Fork 723
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test-sanity.system-JDK8-linux_x86-64 LambdaLoadTest_0 TestStreamOperations OOM #2209
Comments
Restarted the test to see if it fails consistently https://ci.eclipse.org/openj9/view/Test/job/Test-sanity.system-JDK8-linux_x86-64/ |
Its not an intermittent problem. |
@Mesbah-Alam , could you temporarily exclude this test? Thanks. |
Failure is seen in the following sdk :
The LambdaLoadTest falls into the category of "abbs" load tests. This test passed in the last openjdk8 openj9 x64 Linux systemtest build (3 days ago): https://ci.adoptopenjdk.net/view/System%20tests/job/openjdk8_j9_systemtest_x86-64_linux/106/tapResults/ With the following sdk version:
The test also passed in the last (June 15th) openjdk8 hotspot x64 Linux systemtest build: https://ci.adoptopenjdk.net/view/System%20tests/job/openjdk8_hs_systemtest_x86-64_linux/135/tapResults/ I have no problem excluding the test, but just want to make sure- is this really a test issue? Did anything change in the SDK since the last systemtest build was run, where the test had passed? @pshipton |
@Mesbah-Alam, OpenJ9 and Adopt have different test build name. The test failed in OpenJ9 ran with In OpenJ9, this test passed with |
@llxia , Thanks for pointing this out. So, the test only fails with |
Yes, only exclude for that SPEC... and we should verify with a Grinder test at Adopt if we also fail it at Adopt (you can grab the largeHeap build from this job: https://ci.adoptopenjdk.net/view/work%20in%20progress/job/openjdk8_openj9_build_x86-64_linux_largeHeap/) |
Note once the exclude is working in the master branch we'll also want to open a PR against the v0.9.0-release branch. |
I should have looked at the existing PR, which is at AdoptOpenJDK/openjdk-tests, so I guess it applies across all OpenJ9 streams and branches. |
The test has been excluded from OpenJDK 8/9/10 OpenJ9 sdk on Linux x64 non-compressedrefs platforms adoptium/aqa-tests#452 |
Thanks Mesbah. Closing. |
Reopening to track the excluded test. |
The test is being excluded under this closed issue, which implies to me that I should be able to re-enable the test. Was there an actual resolution to this issue? Or a test issue raised? We need to update the |
Reading the earlier comments, I suspect I meant to re-open it but failed to do so. |
See related issue: #2209 with analysis of the test failure. |
@lumpfish I suspect you meant to refer to a different issue in the previous comment, it just refers back to this Issue. |
Could be referring to adoptium/aqa-systemtest#379 and/or adoptium/STF#90. |
Sorry, meant to reference #10638 |
This OOM should no longer occur as a result of the changes made for adoptium/aqa-systemtest#379. |
Test unexcluded via adoptium/aqa-tests#2229 |
https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_special.system_s390x_linux_Release_testList_4/6
@dmitripivkine fyi. probably nothing but just in case. This build is on the 0.28 branches. |
FYI: there is another error as well:
|
Thanks. Opened #13589 to track. |
https://ci.eclipse.org/openj9/job/Test-sanity.system-JDK8-linux_x86-64/5/tapResults/
The text was updated successfully, but these errors were encountered: