-
-
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
AQAvit Triage for January 2023: jdk8u362-b09 #4258
Comments
x86-64_windows sanity.functional - pass
extended.perf seems to be running and passes but does not need to be (as part of a release / AQAvit verification) |
sanity.functional - pass
|
x86-64_mac sanity.functional - pass
|
alpine-linux test jobs can not run due to long-standing issue adoptium/infrastructure#2934 Will need to kick off an AQA_Test_Pipeline with SDK_RESOURCE = customized to hope for test results. SL/Jan24th: Launching via sanity.functional - pass sanity.system - pass sanity.perf - pass sanity.openjdk - pass
|
aarch64_linux sanity.functional - pass sanity.perf - pass extended.openjdk - fail, but with known non-blocking issue (see #4244) |
x86-32_windows sanity.functional - pass
|
ppc64_aix sanity.functional - pass
Possibly related: https://bugs.openjdk.org/browse/JDK-8297141 - in any event, this testcase should not be running against ppc64_aix (see https://github.com/adoptium/jdk8u/blob/master/hotspot/test/runtime/SharedArchiveFile/DefaultUseWithClient.java#L39-L45), not sure why it is, but not valid there. Consider the failure non-blocking. Raised #4270. |
ppc64le_linux sanity.functional - pass
|
x86-64_solaris sanity.functional - pass
|
sparcv9_solaris sanity.functional - pass
jdk/jfr/jcmd/* testcases occasionally coredump executing jcmd (not in all cases, appears to be in cases where JFR.stop is used, needs further investigation):
Try some reruns at TC_Grinder/3116 Also noting the performance degradation between run from September 10th to present day, what changed (new machine config? tests starting to fail, so hitting timeouts? needs investigation): SL/Jan25: noting that we released this platform in October with the same set of failures that have not been addressed or excluded, and while we need to do this (fix or exclude), rather than carry forward each release, we will proceed with releasing this platform despite these failures (related: #4150). |
arm_linux (see #4258 (comment)) |
sanity.functional https://ci.adoptopenjdk.net/job/Test_openjdk8_hs_sanity.functional_arm_linux/285/
extended.functional https://ci.adoptopenjdk.net/job/Test_openjdk8_hs_extended.functional_arm_linux/284/
special.functional https://ci.adoptopenjdk.net/job/Test_openjdk8_hs_special.functional_arm_linux/81/
sanity.openjdk https://ci.adoptopenjdk.net/job/Test_openjdk8_hs_sanity.openjdk_arm_linux/474/
^re-run grinder: https://ci.adoptopenjdk.net/job/Grinder/6408/console --- PASSED sanity.perf https://ci.adoptopenjdk.net/job/Test_openjdk8_hs_sanity.perf_arm_linux/297/
sanity.system https://ci.adoptopenjdk.net/job/Test_openjdk8_hs_sanity.system_arm_linux/271/
^re-run grinder: https://ci.adoptopenjdk.net/job/Grinder/6409/console extended.system https://ci.adoptopenjdk.net/job/Test_openjdk8_hs_extended.system_arm_linux/271/
extended.openjdk https://ci.adoptopenjdk.net/job/Test_openjdk8_hs_extended.openjdk_arm_linux/75/
-https://ci.adoptopenjdk.net/job/Test_openjdk8_hs_extended.openjdk_arm_linux_testList_1/67/
^re-run grinder: https://ci.adoptopenjdk.net/job/Grinder/6415/console
[wen 24th Jan morning]:
-https://ci.adoptopenjdk.net/job/Test_openjdk8_hs_extended.openjdk_arm_linux_testList_2/66/
^re-run grinder: https://ci.adoptopenjdk.net/job/Grinder/6407/console
|
Finished creating related issues, able to close this issue now. |
Unfortunately, due to deleting dry runs on Jenkins and subsequent job IDs starting at 1 again, and adoptium/aqa-test-tools#767, none of the 3 release-jdk8 pipelines are in the TRSS DB (since those 'unique' IDs are already inserted into the DB while monitoring the dry runs). So they will not show up in any of the TRSS views.
This triage will have to be done 'blind' (with no good access to deep history), but by navigating Jenkins jobs.
The text was updated successfully, but these errors were encountered: