-
-
Notifications
You must be signed in to change notification settings - Fork 314
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
hotspot_jre_2 failures jdk8 arm32 hotspot #3297
Comments
Rerunning |
Still fails with the same error. Looking back at the trss link,
|
https://bugs.openjdk.java.net/browse/JDK-8028772 is the closest I could find to a relevant upstream issue; it is simply a discussion of whether G1GC tests should be excluded on armhf. Not sure if that is enough to consider these failures to be non blocking |
Do those tests fail when run against the last GA release? (8u312)? |
Rerunning with last GA release
|
Looks like they all had the same failures. @smlambert are you ok to skip considering these a stop ship on the basis of the re-runs against 8u312 listed above or do you wish to have further investigation? |
The warning and error for
If the test cannot find G1 because it has been disabled, then shouldn't this test be excluded? |
re: #3297 (comment) - we will not block release due to these failures (as its shown, not a regression, that we have already released last GA binaries that fail in the same way). This isn't to say we do not need to do further investigation to understand what next action to take, as these will continue to fail. I have not looked closely at all, but @Haroon-Khel when you look at the test code that prints out the |
@ShelleyLambert Looking at https://github.com/AdoptOpenJDK/openjdk-jdk8u/blob/2544d2a351eca1a3d62276f969dd2d95e4a4d2b6/hotspot/test/gc/g1/mixedgc/TestOldGenCollectionUsage.java#L82, nothing suggests that the option is being ignored. I think that the option is being ignored by the jdk and not by the test code. Do we know why G1 GC is disabled? |
re: #3297 (comment) - sounds like we need a smoke test and a confirmation on which platforms/versions that feature is available in (much like we do for ZGC and Shenandoah features and smoke tests). If its not available on this platform, tests expecting it should certainly be excluded (and expectation it would happen in upstream problem lists, but we can do that in our problem lists first). |
After @sxa's suggestion, rerunning |
The test still fails, but with an error which suggests that it was able to actually run the test
So perhaps this test does not need to be excluded, but we do need to make sure that the right |
Yes, as discussed and lost in a Slack thread somewhere, because this platform is built from a special repo, the build pipeline should get triggered with USE_TESTENV_PROPERTIES=false, so that the test pipelines will use the correct JDK_REPO and the the RELEASE tag of it. |
Running with release tag got the same failures https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/4615/ |
see #4679 (comment) |
3 tests from hotspot_jre_2 in the extended openjdk test suite fail on jdk8 arm32
Failure link https://ci.adoptopenjdk.net/job/Test_openjdk8_hs_extended.openjdk_arm_linux_testList_1/27/
Trss link https://trss.adoptium.net/output/test?id=61f04ed3a7df1a292406cf69
compiler/gcbarriers/PreserveFPRegistersTest.java.PreserveFPRegistersTest
Error log
gc/TestMemoryMXBeansAndPoolsPresence.java.TestMemoryMXBeansAndPoolsPresence
gc/g1/mixedgc/TestOldGenCollectionUsage.java.TestOldGenCollectionUsage
Error log:
Rerunning https://ci.adoptopenjdk.net/job/Grinder/3349/console
The text was updated successfully, but these errors were encountered: