This lead to tier-1 failures on Windows and Solaris platforms. I supposed it is introduced by http://hg.openjdk.java.net/jdk10/jdk10/jdk/rev/f0ab9960bcfd.


#-----testdescription-----
$file=C\:\\jenkins\\workspace\\jdk10-jdk10\\jdk\\test\\java\\lang\\String\\nativeEncoding\\StringPlatformChars.java
$root=C\:\\jenkins\\workspace\\jdk10-jdk10\\jdk\\test
keywords=othervm native
run=USER_SPECIFIED main/othervm/native -Xcheck\:jni StringPlatformChars\r\n
source=StringPlatformChars.java
title=\
#-----testresult-----
description=file\:/C\:/jenkins/workspace/jdk10-jdk10/jdk/test/java/lang/String/nativeEncoding/StringPlatformChars.java
elapsed=35 0\:00\:00.035
end=Mon Jun 19 19\:01\:06 PDT 2017
environment=regtest
execStatus=Error. Use -nativepath to specify the location of native code
harnessLoaderMode=Classpath Loader
harnessVariety=Full Bundle
...
javatestVersion=4.6
jtregVersion=jtreg 4.2 fcs b07
script=com.sun.javatest.regtest.exec.RegressionScript
sections=script_messages build compile
start=Mon Jun 19 19\:01\:06 PDT 2017
test=java/lang/String/nativeEncoding/StringPlatformChars.java
testJDK=C\:\\jenkins\\workspace\\jdk10-jdk10\\build\\jdk
totalTime=36
work=C\:\\jenkins\\workspace\\jdk10-jdk10\\testresults\\windows-x64\\jdk_test.tier1\\jtreg\\JTwork\\java\\lang\\String\\nativeEncoding