valid tags for jtreg-6+1

Vitaly Provodin vitaly.provodin at jetbrains.com
Mon Jun 7 04:17:39 UTC 2021


Hi all,

Launching tests against a fork of https://github.com/openjdk/jdk I got the following excettion

java.lang.IllegalArgumentException: 6+1
   at com.sun.javatest.regtest.tool.Version.<init>(Version.java:80)
   at com.sun.javatest.regtest.config.TestProperties$Cache$Entry.initAllowSmartActionArgs(TestProperties.java:452)
   at com.sun.javatest.regtest.config.TestProperties$Cache$Entry.<init>(TestProperties.java:262)
   at com.sun.javatest.regtest.config.TestProperties$Cache.getEntryInternal(TestProperties.java:509)
   at com.sun.javatest.regtest.config.TestProperties$Cache.getEntry(TestProperties.java:500)
   at com.sun.javatest.regtest.config.TestProperties.<init>(TestProperties.java:57)
   at com.sun.javatest.regtest.config.RegressionTestSuite.<init>(RegressionTestSuite.java:80)
   at com.sun.javatest.regtest.config.RegressionTestSuite.open(RegressionTestSuite.java:65)
   at com.sun.javatest.regtest.config.TestManager.getTestSuites(TestManager.java:165)
   at com.sun.javatest.regtest.tool.Tool.run(Tool.java:1124)
   at com.sun.javatest.regtest.tool.Tool.run(Tool.java:1075)
   at com.sun.javatest.regtest.tool.Tool.main(Tool.java:147)
   at com.sun.javatest.regtest.Main.main(Main.java:58)

It happened after the fix for https://bugs.openjdk.java.net/browse/JDK-8266254 <https://bugs.openjdk.java.net/browse/JDK-8266254> which includes the change in TEST.ROOTs

# Minimum jtreg version
requiredVersion=6+1

Unfortunately I could not download a new build of jtreg from https://ci.adoptopenjdk.net/view/Dependencies/job/jtreg because of the error: “HTTP ERROR 404 Not Found”.
So I decided to build jtreg by my self but got the same exception with slightly different description

java.lang.NumberFormatException: For input string: "jtreg6"
   at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
   at java.base/java.lang.Integer.parseInt(Integer.java:652)
   at java.base/java.lang.Integer.parseInt(Integer.java:770)
   at com.sun.javatest.regtest.tool.Version.parseDottedInts(Version.java:166)
   at com.sun.javatest.regtest.tool.Version.compareTo(Version.java:185)
   at com.sun.javatest.regtest.tool.Tool.run(Tool.java:1131)
   at com.sun.javatest.regtest.tool.Tool.run(Tool.java:1079)
   at com.sun.javatest.regtest.tool.Tool.main(Tool.java:148)
   at com.sun.javatest.regtest.Main.main(Main.java:58)

Looking into sources it was found out that build version is taken from the latest line of `git tag` output

$ git tags
jtreg-6+1
jtreg4.1-b01
. . .
jtreg5.1-b01
jtreg6

Notes:
1. jtreg6 and jtreg-6+1 pointed to the same revision

2. jtreg-6+1 is not the latest in the output

3. TAG_INFO was parsed as follows for each of these tags
$ echo jtreg6 | sed 's/jtreg\([0-9]\.[0-9]\)-\(b[0-9]*\).*/\1/‘
jtreg6
$ echo jtreg-6+1 | sed 's/jtreg\([0-9]\.[0-9]\)-\(b[0-9]*\).*/\1/'
jtreg-6+1

After adding tag jtreg6.1-b01 at the same revision I got a build which successfully starts the tests.

It looks like some where there is an issue in jtreg tagging
If my suspicious are correct then could somebody check tags in jtreg?

Thanks,
Vitaly


More information about the jtreg-dev mailing list