-
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
[23.1] Backport: svm: adopt "JDK-8328366: Thread.setContextClassloader from thread in FJP commonPool task no longer works after JDK-8327501" #780
[23.1] Backport: svm: adopt "JDK-8328366: Thread.setContextClassloader from thread in FJP commonPool task no longer works after JDK-8327501" #780
Comments
See also #739 (comment) |
FWIW "upstream repo" is meant to refer to https://github.com/oracle/graal/, the aim of this question was/is to see if the backport request is regarding a fix that is already accepted upstream or a backport of a Mandrel-specific fix (from a different branch). |
Shouldn't matter in this case, then. As the answer is no in both cases. |
Upstream PR: graalvm/graalvm-community-jdk21u#6 |
I'll re-open since we still need to merge in the upstream changes into the 23.1 release branch. |
#786 is the merge from upstream. |
#786 is merged. Work completed. |
What would you like to backport?
We need to backport oracle@10bb0c6 to the Mandrel 23.1 release tree (probably via the upstream repo).
Why?
Since the
JDK 21.0.5+3
EA build we see test failures in quarkus native integration tests. For examplequarkus-integration-test-micrometer-prometheus
, which fails with a segfault like so:See https://github.com/graalvm/mandrel/actions/runs/10427964088/job/28884041672
Are the changes being backported merged in upstream Graal?
The text was updated successfully, but these errors were encountered: