[YETUS-943] Test patch fails to extract version information from a JDK11 jvm

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.11.1
• Fix Version/s: 0.12.0
• Component/s: Precommit

Release Note

<!-- markdown -->
This patch alters `report_jvm_version` to extract JVM vendor and version information from Java system properties. It now returns a string that is the concatenation of verdor and runtime versions.

• Assignee: Nick Dimiduk
• Reporter: Nick Dimiduk
• Created: 20/Feb/20 22:38
• Updated: 03/Oct/20 06:37
• Resolved: 17/Mar/20 18:44

Description

Trying to use pre-commit with AdoptOpenJDK11 in the test matrix, the logic for extracting the version information is incorrect.

For JDK8, the output is

root@ab2cb99dbf34:/# /usr/lib/jvm/jdk8u232-b09/bin/java -version
openjdk version "1.8.0_232"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_232-b09)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.232-b09, mixed mode)

which Yetus parses as "1.8.0_232".

For JDK11, it's

root@ab2cb99dbf34:/# /usr/lib/jvm/jdk-11.0.6+10/bin/java -version
openjdk version "11.0.6" 2020-01-14
OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.6+10)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.6+10, mixed mode)

which Yetus parses as "2020-01-14".

Issue Links

• contains: YETUS-13 The different JDKs which versions are the same aren't distiguished on multi-JDK mode
• relates to: HBASE-22972 [JDK11] Support JDK11 LTS in HBase
• links to: GitHub Pull Request #91
• links to: GitHub Pull Request #1214
• links to: GitHub Pull Request #1237