-
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] Sync with upstream for July 2024 CPU #771
[24.0] Sync with upstream for July 2024 CPU #771
Conversation
…eferences to contexts on the engine.
(cherry picked from commit c558689)
(cherry picked from commit 1c37f51)
(cherry picked from commit f0a6a9c)
(cherry picked from commit 83b936a)
PullRequest: graal/17509
…bility comparisons PullRequest: graal/17500
(cherry picked from commit 6be8047)
(cherry picked from commit 8acba5c)
…ummary. PullRequest: graal/17502
…ion 18.20.2. PullRequest: js/3122
… tear-down. (cherry picked from commit 8319494)
(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)
PullRequest: graal/17607
PullRequest: graal/17492
(cherry picked from commit 813d8d7)
(cherry picked from commit 240f142)
68b478d
to
b383a25
Compare
Build fails with:
Looking |
Merged cleanly except for: 1. oracle@7c93032 which conflicts with our earlier backport in graalvm#722. To deviate as little as possible from upstream I dropped our backport in favour of the upstream one. 2. The suite files were updated to match the Mandrel version scheme, i.e. the version is set to 24.0.2.0 instead of 24.0.2, and the Release value is set to False.
b383a25
to
0b56897
Compare
CI failure is:
It's irrelevant to this sync. I will backport graalvm/mandrel-packaging#435 to Update: The backport PR is graalvm/mandrel-packaging#438 |
@zakkak Could you please trigger another CI run. The Mandrel IT failure should be gone with the backport. |
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.
This seems OK. Please trigger a CI run which should be clean before we merge.
maven-tooling failed due to:
Rerunning only the corresponding batch of tests, should take ~1 hour |
Looks good now. |
Thx. |
Sync with upstream 'oracle/release/graal-vm/24.0' for July 2024 CPU
Merged cleanly except for:
oracle@7c93032 which conflicts with our earlier backport in [24.0] Adopt "JDK-8324646: Avoid Class.forName in SecureRandom constructor" #722. To deviate as little as possible from upstream I dropped our backport in favour of the upstream one.
The suite files were updated to match the Mandrel version scheme, i.e. the version is set to 24.0.2.0 instead of 24.0.2, and the Release value is set to False.