> On 12 Jan 2017, at 12:51, Alan Bateman <[email protected]> wrote: > > > > On 12/01/2017 10:43, Staffan Larsen wrote: >> jtreg 4.2 b05 was recently promoted with some important fixes. Please review >> the change below to upgrade jdk9-dev to the new version. I have run >> jdk-tier1, jdk-tier2 and jdk-tier3 on linux and os x with this change and >> did not see any new test failures. >> >> Thanks, >> /Staffan >> >> >> diff --git a/common/conf/jib-profiles.js b/common/conf/jib-profiles.js >> --- a/common/conf/jib-profiles.js >> +++ b/common/conf/jib-profiles.js >> @@ -870,7 +870,7 @@ >> jtreg: { >> server: "javare", >> revision: "4.2", >> - build_number: "b04", >> + build_number: "b05", >> checksum_file: "MD5_VALUES", >> file: "jtreg_bin-4.2.zip", >> environment_name: "JT_HOME", > This looks okay for infrastructure that uses this file but don't you need to > bump the requiredVersion in each test root to force its usage in other > contexts?
I don’t know if there are any tests that rely on functionality in 4.2 b05. If there are, we need to bump requireVersion, yes. I only know that the infrastructure needs 4.2 b05. /Staffan
