-
Notifications
You must be signed in to change notification settings - Fork 15
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
[24.0] Undefined reference to `Java_java_lang_VirtualThread_notifyJvmtiDisableSuspend' with JDK 22+31 #661
Comments
Fixed upstream in oracle#8140 and backported to 24.0 with oracle@96e2820 and oracle@bb02595 Rebasing mandrel/24.0 on upstream. CI testing the rebase https://github.com/graalvm/mandrel/actions/runs/7538951835 |
It still seems there?
|
Running with Upstream seems to still build against 22+27 while the latest labsjdk 22 build is 22+29. So the issue is probably present in upstream as well. |
Did you report this upstream yet? |
No, I am not sure what would be the value of reporting this upstream at the moment. |
#661 (comment) mentions that the back-ports are supposed to fix this problem for 22+31, correct? They don't. If that's the case isn't it worth asking/reporting this upstream? Up to you, though. |
@gilles-duboscq FYI: It looks like the backport of oracle#8140 is not enough to build with JDK 22+31. Is there any ETA on when you plan to bump labsjdk to 22+31 for the Thanks |
I've filed oracle#8195 for this. |
@jerboaa I have cherry picked oracle@944f5d1 in https://github.com/graalvm/mandrel/tree/mandrel/24.0 to temporarily (the cherry-pick will be dropped once backported on upstream) work around oracle#8195 and be able to get some more meaningful test results. |
OK, thanks! I'll close this as we have better CI results by now showing that this issue is no longer there: |
I prefer to keep this open till the fix gets backported upstream as well. The cherry pick was mostly to get the CI working again. In the highly unlikely case that upstream doesn't get a backport to fix this, we will need a proper backport PR to close this issue (but since the branch is far from stable at this point I prefer to keep the rebase/force-push approach with work-arounds cherry-picked on top for the time being, happy to discuss alternatives though). |
Sure. |
Fix merged upstream in 24.0 as part of oracle@77f95e2 I have rebased mandrel/24.0 and dropped my cherry pick. Closing this. |
Description
We see CI failures due to
The new method was introduced with a backport of https://bugs.openjdk.org/browse/JDK-8311218 in JDK 22+31
The text was updated successfully, but these errors were encountered: