-
Notifications
You must be signed in to change notification settings - Fork 729
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Java 12 functional sanity failure JCL_Test test_toLowerCase_lithuanian #4659
Comments
@pshipton given it's Lithuanian the JIT won't do any intrinsics here so this will likely fail with On another thought it seems that we already have coverage for Do any of you (@DanHeidinga @pshipton @theresa-m @JasonFengJ9) have any objections to simply removing the test given the above justification? |
Java 12 moved to Unicode 11.0.0 from 10.0.0. @fjeremic are you ok with not having any PR testing for toUpper/LowerCase? Does the JIT affect these results? I'm thinking we should just remove the Lithuanian sub-test for now. I'm concerned about the timing of anybody noticing one of these failing tests at Adopt. Getting these tests into an "always green" state is WIP. Until we reach that goal I'm not sure how long it would take before a failure would be noticed and brought to our attention. |
https://ci.adoptopenjdk.net/view/Test_openjdk/job/openjdk11_j9_openjdktest_x86-64_linux/277/testReport/java_lang_Character_UnicodeCasingTest/java/UnicodeCasingTest/ is passing for jdk11, and we have not turned on jdk12 builds yet at Adopt so have not seen the UnicodeCasingTest fail yet. At the moment, all sanity.openjdk tests (3,262 tests, which include the UnicodeCasingTest) are passing. If we turn on jdk12 and have only a handful of failures to triage, it would be reported fairly quickly. Unknown amount of time if there are many failures to triage initially. |
@pshipton we already added unit tests for the JIT intrinsics as part of #2098. See [1] for the tests that were added. The tests in Test_String.java are more so for the
@smlambert they won't fail at Adopt because presumably the OpenJDK tests have been updated to the new Unicode 11.0.0 standard and because our String implementation uses OpenJDK It's just the fact that we have our own special Lithuanian tests (in OpenJ9) that we're having to maintain at each JDK level which updates which Unicode standard we use. We should just remove our special testing and let OpenJDK test it for us for free. |
AdoptOpenJDK testing already has coverage for all locales and the various special cases, including Lithuanian. Since Java 9 onward we have started to use the OpenJDK implementations for `toUpperCase` and `toLowerCase`. As such we will pick up updated test material from Adopt whenever the Unicode version changes in future Java releases and we will not have to continuously update these Lithuanian tests. See the discussion in eclipse-openj9#4659 for further details and examples of tests. Fixes: eclipse-openj9#4659 Signed-off-by: Filip Jeremic <[email protected]>
Yes, I understand, thanks. I was just reporting that we have no jdk12 builds yet and that the tests will run nightly (as they are part of sanity.openjdk) when we do. |
I ran a Java 12 functional sanity test using the changes from #3980 and #4531.
https://ci.eclipse.org/openj9/job/Test-sanity.functional-JDK12-linux_390-64_cmprssptrs/3
JCL_Test_0 JCL_Test_1
The text was updated successfully, but these errors were encountered: