Closed JasonFengJ9 closed 4 months ago
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.
Removed the test. https://github.ibm.com/runtimes/SVTTestRepo/pull/113
For future reference see infrastructure/issues/9118
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.