JDK-8076290 : JCK test api/xsl/conf/string/string17 starts failing after JDK-8074297
  • Type: Bug
  • Component: xml
  • Sub-Component: jaxp
  • Affected Version: 9
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2015-03-31
  • Updated: 2015-09-29
  • Resolved: 2015-04-01
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7 JDK 8 JDK 9 Other
6u101Fixed 7u85Fixed 8u51Fixed 9 b59Fixed openjdk7uFixed
Related Reports
Relates :  
JDK-8074297 - substring in XSLT returns wrong character if string contains supplementary chars
Description
api/xsl/conf/string/string17_string17 TestCase [testTransformation] 
This JCK test starts failing in corelibs jdk9 nightly testing on all platforms after JDK-8074297

java version "1.9.0-ea" 
Java(TM) SE Runtime Environment (build 1.9.0-ea-langtools-nightly-h2444-20150330-b57) 

JCK suite info: 
JCK version: 9/b09

----------out1:(2/168)----------
testTransformation: Failed. Transformation result is not equal to expected result.
STATUS:Failed.test cases: 1; all failed; first test case failure: testTransformation
----------out2:(12/306)----------
mismatch-value;TEXT()len=2;TEXT()len=3;lengths do not match
mismatch-value-gold;TEXT();
12
mismatch-value-text;TEXT();
123
XHTFileCheckService results were not equal.
Expected result:
<?xml version="1.0" encoding="UTF-8"?>
<out>12</out>

Actual result:
<?xml version="1.0" encoding="UTF-8"?><out>123</out>
result: Failed. test cases: 1; all failed; first test case failure: testTransformation
Comments
The fix differs from suggested earlier and it's under the review now: http://mail.openjdk.java.net/pipermail/core-libs-dev/2015-March/032644.html
31-03-2015
Incorrect variable was used during the fix for JDK-8074297: int offset = value.offsetByCodePoints(istart, ilength); Should be replaced with int offset = value.offsetByCodePoints(istart, isum); Will update the 8074297 test and fix the source code. Thanks for catching this.
31-03-2015