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
FVT_Serviceability.diagnostics ERROR: Incorrect JIT Version Information in ENVINFO section. JIT information in javacore was 'tr.open_20240522_180822_aa580a0', expected it to contain 'aa580a0dc7f'
#19550
Closed
JasonFengJ9 opened this issue
May 24, 2024
· 2 comments
java version "1.8.0_421"
Java(TM) SE Runtime Environment (build 8.0.9.0 - pxp6480sr9-20240514_01(SR9))
IBM J9 VM (build 2.9, JRE 1.8.0 Linux ppc64-64-Bit 20240523_71544 (JIT enabled, AOT enabled)
OpenJ9 - aa580a0dc7f
OMR - cba5328
IBM - 3c87141)
JCL - 20240513_01 based on Oracle jdk8u421-b05
Optional info
Failure output (captured from console output)
>> 2024 Thu May 23 23:12:01 javacore-0001.txt: ERROR: Incorrect JIT Version Information in ENVINFO section. JIT information in javacore was 'tr.open_20240522_180822_aa580a0', expected it to contain 'aa580a0dc7f'
*********************************************************************************
>> 2024 Thu May 23 23:12:01 Axxon_dump_request.pl TEST SUMMARY - ALL TESTS FAILED
I believe you get a longer SHA when there is a conflict with the shorter one. Likely in the next builds there won't be another conflict and the tests will not fail. In the long term we should update the test to be more flexible so it doesn't fail when a longer SHA is used in the -version output.
Failure link
From an internal build(
rhel7p8vm02
):Optional info
Failure output (captured from console output)
Also occurred at Linux PPC LE 64bit Compressed Pointers
Linux PPC
Win64 Hammer
They all have OpenJ9 SHA
aa580a0dc7f
while other passing JVMs have SHAsaa580a0
that the test expects.The text was updated successfully, but these errors were encountered: