-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
TEST: java/util/Locale/LocaleCategory.java failed with jdk_util_j9: ubuntu, openj9, 11 |15 #59
Comments
Also seen on AdoptOpenJDK jdk15 nightly build: https://ci.adoptopenjdk.net/job/Test_openjdk15_j9_sanity.openjdk_x86-64_linux/152/consoleFull |
@lumpfish it's running on git-hub runner, shouldn't be docker. |
This has been seen on multiple systems where My feeling is that we should be able to run these tests on any system in any locale and if we don't we have a bug that needs to be resolved. We cannot assume that anyone who wants to run our tests suites is in the US! While setting that locale on the systems affected as a global would likely resolve it it does not feel like the right solution as it is simply masking the problem. We should either
|
The test material in question is from OpenJDK. Agree that making the test more resilient to any environment is optimal. Historically, when we have suggested upstream OpenJDK tests contain more logic to 'do the right thing', it was met with a different philosophical approach than you have suggested. (In a different issue regarding jdi tests where we thought tests should clean up stray processes they started, the JBS issue was closed with a note that said its up to the person running the test to do such activities). I am happy to always start with the attempt to report/fix the test at the source (as described in our Triage guidelines), in this case in OpenJDK. |
I'm not sure if it's the test case issue as the test never has issue with hotspot impl with the exact same environment as far as I know. It looks likely there's some difference between hotspot and openj9 underlying? |
If that's true (and a quick scan through our logs suggests it's on jdk_util_j9_0 in sanity.openjdk on JDK11+ - have not seen it on 8 so far) it sounds like we need to raise with OpenJ9 ... @pshipton is this something you're aware of and if it's not something obvious shall we raise an issue against OpenJ9? |
Please open an OpenJ9 issue. I can reproduce the problem on Ubuntu (16) by exporting |
Issue opened in eclipse-openj9/openj9#11620, Keep this open for verification. |
The OMR change has promoted, should be fixed in the next build. |
Test passed. Close it. |
Test failed:
#24 (comment)
Initial investigation:
#24 (comment)
#24 (comment)
The text was updated successfully, but these errors were encountered: