-
Notifications
You must be signed in to change notification settings - Fork 13
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
Merge upstream vm-23.1.5 tag 1st batch #46
Merge upstream vm-23.1.5 tag 1st batch #46
Conversation
(cherry picked from commit a44a8d3)
(cherry picked from commit e9e411e)
(cherry picked from commit a7b524e)
(cherry picked from commit 2a2d7bb)
(cherry picked from commit 6a5861e)
(cherry picked from commit 1b7238b)
(cherry picked from commit 77b88cc)
(cherry picked from commit 58d0dbb)
(cherry picked from commit 4fdcc7c)
(cherry picked from commit 05e25e0)
(cherry picked from commit a54f2eb)
(cherry picked from commit de74c30)
(cherry picked from commit 534b97a)
(cherry picked from commit e9baa36)
(cherry picked from commit 317c1b9)
(cherry picked from commit 590874b)
(cherry picked from commit c558689)
(cherry picked from commit 1c37f51)
… tear-down. (cherry picked from commit 8319494)
(cherry picked from commit eef8d9a)
…nchronized blocks. (cherry picked from commit 25f7ffc7731fe3224446ad338a7c447c4df8332c)
…ode. (cherry picked from commit 7922f87b7e2cf44f084a1ea359da0c3643d269b3)
Hi @JohnTortugo @bulasevich can you please review? For more details about the process I followed see #37 |
Thanks for splitting the original PR into smaller, more manageable pieces. I reviewed the changes and confirmed that they are consistent with the related GR pull requests. Everything looks good to me - no objections. Could you share how you tested the change? |
Thank you @zakkak . I'm going to take a look at the changes today and also trigger some internal tests. |
Other than local builds and some trivial smoke tests, the changes are being tested using github actions, see https://github.com/graalvm/graalvm-community-jdk21u/actions (we need to update the Quarkus nightly workflow btw). When reviewing a PR can you please indicate your approval (or request for changes) using the GitHub UI as well? You can do so by clicking on the "Files Changed" tab and then on the green button "Review Changes". Unfortunately I cannot explicitly add you as reviewers through the UI. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I only looked at native-image and compiler parts (ignored truffle stuff). Seems OK to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thank you.
I tested LibGraal JIT with OpenJDK JTREG tier1-4 and JCK using Parallel, Serial and G1GC on ARM64 and x86_64. All tests were on Amazon Linux 2. I also did some sanity check tests on GraalJS.
1st batch of #37
Backports:
Note
eed5f79a666 [GR-52780] Backport to 23.1: FileSystemsTest#testSetAttribute() fails on JDK-23-linux.
is not part of this backport because it has been separately backported in #20The backports are clean, there were no conflicts.