Closed jerboaa closed 2 months ago
Assuming the upstream repo is graalvm-community-jdk21u:
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).
Assuming the upstream repo is graalvm-community-jdk21u:
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.
I'll re-open since we still need to merge in the upstream changes into the 23.1 release branch.
https://github.com/graalvm/mandrel/pull/786 is the merge from upstream.
https://github.com/graalvm/mandrel/pull/786 is merged. Work completed.
What would you like to backport?
We need to backport https://github.com/oracle/graal/commit/10bb0c6797753cd21ceef3bd2228f66dc73969e0 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?