-
-
Notifications
You must be signed in to change notification settings - Fork 243
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
openjdk8 HotSpot win32 builds are failing. #384
Comments
@smlambert I'm sure I saw you producing win32 builds in a recent bunch of updates? |
I was actually focussed on the openjdk8-openj9 builds for win32 (as part of the openj9 0.9 release), which are building, being tested and published to the website. I haven't looked at why the openjdk8 (with hotspot) are not compiling. I can see if I notice anything obvious, but I think it was @sxa555 that enabled those builds originally. |
@smlambert how did you publish win32 builds? Could you share the link please? I can't find any win32 release. There is no link to download win32 binaries on this page: https://adoptopenjdk.net/releases.html?variant=openjdk8 |
@gdams many thanks for this info. Have you declined openjdk8 hotspot support for 32-bit platforms? |
Nope, but it's not our biggest priority, please do join our community at adoptopenjdk.net/slack if you can help! |
@cruzy I created that job in jenkins at a similar time to creating the openj9 one. We have so far never had fully working builds with hotspot. As @karianna says we have had specific requests from openj9 to have win32 builds but no-one's so far shouted for hotspot ones, although I'd like us to have parity across the VMs. Out of interest, what's your need for 32-bit hotspot - is it some specific hardware you're using? [EDIT: I've moved the win32 hotspot builds out of the main build page - they shouldn't have been shifted from the work in progress tab] |
@karianna thank you for this offer, I would like to join the community if we decide to choose AdoptOpenJDK as a primary JRE in our product.
That's why I want to try your hotspot version on x32 JRE. |
I would also really like to hear about what problems you encounter with the AOJ 8x32 with openj9 builds so they can be addressed, if you can or wish to articulate them. |
I echo @smlambert's comment but for the x64 JRE - unless you're using 32-bit native JNI code with it the 64-bit one should work ok and if there's any issue please let us know. |
(FYI I've tried another HotSpot win32 build run and it's failed in a different place from what it did previously so will still need some investigation and debugging to get that through - it's running on the same build machine as the openj9 win32 build so the environment should be the same) |
Hi, we are considering AdoptOpenJDK as an alternative JVM due to LTS policy changes by Oracle. Unfortunately some of our clients are still stuck on Win32, and we would like to limit the number of JVMs we test on and support, hence we would go only for Hotspot for now (which also seems to be a safer transition). For us a Win32 Java 8 Hotspot release in time before 2019 January (end of updates from Oracle) seems to be the missing piece for a complete solution. |
We've asked the Main Adopt community directly, as of yet no volunteers. I've cast the net out further to the Java User Groups and Java Champions lists. |
Now that openjdk8_build_x86-32_windows build went green (currently sticked to win2008 build agent that also builds x86-64) and having a related openjdk8_hs_openjdktest_x86-32_windows build, I believe it's now time to have related win32 build definitions to be part of the #462 is the related PR. |
Hi, we have the question if the JavaFX components will be part of this distribution as well ? Currently in the nightly we don`t see it. |
Closing this issue as done. @Capa83 Can you please raise a separate issue for JavaFX support? |
Ok, will do! |
https://ci.adoptopenjdk.net/job/openjdk8_build_x86-32_windows/ - these builds are failing for a month.
Also, these builds are not accessible on your site. Please, do not drop x32 support, it is still required.
The text was updated successfully, but these errors were encountered: