-
Notifications
You must be signed in to change notification settings - Fork 733
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
jdk_foreign_1_FAILED java/foreign/StdLibTest.java IllegalArgumentException: Unsupported charset: windows-1252 #20337
jdk_foreign_1_FAILED java/foreign/StdLibTest.java IllegalArgumentException: Unsupported charset: windows-1252 #20337
Comments
Issue Number: 20337 |
This must be due to my change in ibmruntimes/openj9-openjdk-jdk23#52 which gets the native encoded string before calling native printf through downcall. I will take a look at this on Tuesday. |
Looking at the JDK23 failing stack, it fails in [1], and I do not see support for any charset other than UTF , ISO-8859. I need go through the code to see how to fix this properly (I believe, on windows, having standard UTF-8 charset should be fine, but given that we pass in native charset on windows, it fails. @JasonFengJ9 / @pshipton is this going to block 0.48 ? If yes, I can go ahead and revert the changes to ensure it works fine and work on more concrete fix. Similar change went in JDK21 but it is OK there as we simply get the bytes in native encoding from given string and allocate segment using that, so we would not hit the issue. FYI, @keithc-ca |
The test will need to be updated;
|
Yes, this was my first instinct. If native charset is not standard, it should go on and allocate using default charset (Which is UTF-8), this would resolve current failure. And update the code for z/OS later. |
This is a test issue, it won't block 0.48. |
If native encoding charset is not one of the standard charset, allocate segment using default charset for printf down call in StdLibTest. Fixes: eclipse-openj9/openj9#20337 Signed-off-by: Rahil Shah <[email protected]>
If native encoding charset is not one of the standard charset, allocate segment using default charset for printf down call in StdLibTest. Fixes: eclipse-openj9/openj9#20337 Signed-off-by: Rahil Shah <[email protected]>
If native encoding charset is not one of the standard charset, allocate segment using default charset for printf down call in StdLibTest. Fixes: eclipse-openj9/openj9#20337 Signed-off-by: Rahil Shah <[email protected]>
If native encoding charset is not one of the standard charset, allocate segment using default charset for printf down call in StdLibTest. Fixes: eclipse-openj9/openj9#20337 Signed-off-by: Rahil Shah <[email protected]>
If native encoding charset is not one of the standard charset, allocate segment using native encoded bytes for the string for printf down call in StdLibTest. Fixes: eclipse-openj9/openj9#20337 Signed-off-by: Rahil Shah <[email protected]>
Issue Number: 20337 |
1 similar comment
Issue Number: 20337 |
Allocate segment using native encoded bytes for the string for printf down call in StdLibTest. Fixes: eclipse-openj9/openj9#20337 Signed-off-by: Rahil Shah <[email protected]>
Failure link
From internal Test_openjdk23_j9_sanity.openjdk_x86-64_windows_testList_6 (win10x86-rtp-rt5-1)
Rerun in Grinder - Change TARGET to run only the failed test targets
Optional info
Failure output (captured from console output)
50x internal Grinder - all failed
The text was updated successfully, but these errors were encountered: