-
Notifications
You must be signed in to change notification settings - Fork 138
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] General Release Activities #2213
Comments
gathering some links now that building, full testing and provisioning are becoming the bottle neck towards Java 23 GA: Tests❌ currently 478 failures, some fresh, some older then the job history on jenkins
Update sitehttps://download.eclipse.org/eclipse/updates/4.33-Y-builds/
Patch builds
TODOs
|
I came to conclude that this is a JIT bug in JDK 23 ea. The following option avoids the problem:
We should consider:
|
The Y-builds job claims to run daily ("Daily Maintenance Builds"), but the last runs where only these:
Seemingly caused by this change: https://ci.eclipse.org/releng/job/YPBuilds/job/Y-build-4.33/jobConfigHistory/showDiffFiles?timestamp1=2024-08-23_10-00-01×tamp2=2024-08-31_13-20-18 I kindly ask to ensure that daily really means daily from now on. |
Scheduled it to run daily. |
Raised eclipse-platform/eclipse.platform.releng.aggregator#2340 for this.
Checking with @sravanlakkimsetti on how to go about this. Will take this up with his inputs. |
I made local experiments with hand-crafted meta data like these:
Replace the three all-caps placeholders with real values and that should be it. I also played with adding this in
Not sure if that is of any value, though :) (since the dependency is already present in the ..core.manipulation plugin). |
For posterity:
So even if ideas exist to improve this, we seem to be good for this iteration. Actually it's a rare situation that new dependencies will be added on behalf of a feature patch. And finally, some hints on building the patch feature locally:
@merks reported success with this command;
|
Addressed in #2954 |
Finally the workaround for the JIT-bug worked leaving us with only 3 failures in JDT, all in ASTRewritingModifyingCopyTest. And guess what: all three show the infamous NPE without any
So o.e.j.c.tests.model needs the same JIT workaround, too. |
Done with #2957 |
Fresh status update: Testshttps://ci.eclipse.org/releng/job/YPBuilds/job/ep433Y-unit-cen64-gtk3-java23/26/testReport/ lists only a single test failure:
Ergo: From a test suite p.o.v. we are good to go! ✔️ Update siteHad already been successful during my previous summary. ✔️ Patch buildAlso patch builds run daily now at 5am and will pick up the Y-build of the previous day.
Installation from https://download.eclipse.org/eclipse/updates/4.33-P-builds/ succeeds and passes smoke tests. ✔️ JIT-bug workaroudAs mentioned, the landslide of failures in our test suite was caused by a JIT bug in JVM 23. As a bonus feature, installing jdt.core now automatically adds the matching workaround into eclipse.ini, to make running Eclipse on Java 23 safe. ✔️ |
The feature has been released and shipped. |
Top Level for bug general release activities for #2212
Increase the bundle service version
This must not use the same version as the base. As always, we increase the service segment by 50 for the beta work ==> 3.x. 50
(e.g. 0 -> 50, 1 -> 50, 100 -> 150).
Tasks:
refer: [A similar work]
(Also similar work in previous release
After this:
The text was updated successfully, but these errors were encountered: