-
-
Notifications
You must be signed in to change notification settings - Fork 314
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
Failing jdk_time test on MacOS x64 JDK18+36 release triage #3498
Comments
Many upstream bugs concerning timeout failures can be found, but none with this error |
Adding the jtr file (from the test output archive) for reference: TestZoneTextPrinterParser.jtr.txt |
Also noting that this test consistently passes in jdk17 (https://ci.adoptopenjdk.net/job/Test_openjdk17_hs_extended.openjdk_x86-64_mac_testList_1/38/testReport/java_time_test_java_time_format_TestZoneTextPrinterParser/). Run against Oracle's jdk18 build here: https://ci.adoptopenjdk.net/job/Grinder/3937/ |
We should also double-check that there is no 'test skew'... that the test material we are using, matches up with the source build tag being tested. (believe this to be the case, but will confirm). |
@sophia-guo - you mentioned this test case, DateTimeParseException is also failing on win32? |
Not the same tests, the underlying failure is the same java.time.format.DateTimeParseException. Test : test.java.time.format.TestUnicodeExtension.java |
test.java.time.format.TestUnicodeExtension.java against azul on win32 got the same failure https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/3962/consoleFull |
Ok, so we are going to treat it as 'non-blocking', but I'd like to figure out if this is a test case that needs to be improved, or a product problem that should be fixed (or skew/mismatch of test material). |
This should not be
|
test.java.time.format.TestUnicodeExtension has not been updated for two years. java/time/test/java/time/format/TestZoneTextPrinterParser.java did have updated recently with jdk source code update. Also it is related with adoptium/jdk18u@064ee6a or https://bugs.openjdk.java.net/browse/JDK-8177819 Also https://bugs.openjdk.java.net/browse/JDK-8177819 only delivered to jdk18, no backport to jdk17, which explains why tests passed on jdk17. |
@jiekang , @andrew-m-leonard Based on #3498 (comment) it might be helpful to open a JBS issue? |
@sophia-guo to clarify, you suspect changes from JDK-8177819 are causing the failure in 18, and since it's not backported to 17, it's still passing there. Is that right? |
Yes, correct. @jiekang |
Just noting, the test that fails in TestZoneTextPrinterParser didn't exist in 17, it was added by https://bugs.openjdk.java.net/browse/JDK-8177819 (openjdk/jdk@a363b7b#diff-d4fb442a77ecfe0a5c7ab7dbc30acdeb8aee1d001f4f0555b5e0d50bfd5c9047R261) |
|
This is the same problem as https://bugs.openjdk.java.net/browse/JDK-8282023 To recreate:
Using Locale.ROOT fix:
|
Opened JBS bug: https://bugs.openjdk.java.net/browse/JDK-8283842 |
@andrew-m-leonard #3494 has same issue, which is on win32. Noticed https://bugs.openjdk.java.net/browse/JDK-8283842 only mentioned Macos. |
@sophia-guo I added a comment on seeing it on win32. |
Fixed upstream: openjdk/jdk@a41550b |
Any plan to back port to jdk18? @andrew-m-leonard |
I've asked upstream.. |
I don't expect this to be backported to 18, but I don't think it matters to us. @sophia-guo can this issue be closed? |
Yes, no need to backport to 18 any more. Close it. |
java/time/test/java/time/format/TestZoneTextPrinterParser.java.TestZoneTextPrinterParser from jdk_time in the extended openjdk test suite is failing on MacOS
Test job link https://ci.adoptopenjdk.net/job/Test_openjdk18_hs_extended.openjdk_x86-64_mac_testList_1/26/testReport/
Trss link https://trss.adoptium.net/output/test?id=623b273c72761a4c5cf83036
I reran the job on test-macstadium-macos1014-x64-4, https://ci.adoptopenjdk.net/job/Grinder/3917/console, it still failed. I am rerunning it on a build machine to double check https://ci.adoptopenjdk.net/job/Grinder/3932/console
The text was updated successfully, but these errors were encountered: