Declare 4.26 RC1

[SDawley]

A "go" is needed from all the components below to declare this milestone.

Current Candidate

Eclipse downloads:
https://download.eclipse.org/eclipse/downloads/drops4/I20221117-1330

Build logs and/or test results (eventually):
https://download.eclipse.org/eclipse/downloads/drops4/I20221117-1330/testResults.php

Software site repository:
https://download.eclipse.org/eclipse/updates/4.26-I-builds

Specific (simple) site repository:
https://download.eclipse.org/eclipse/updates/4.26-I-builds/I20221117-1330

Equinox downloads:
https://download.eclipse.org/equinox/drops/I20221117-1330

---

Deadlines:

• Friday, 2022-November-18, around 1 AM (Eastern): deadline for sign-off (or, by then, comment in this issue when you expect to sign-off).
• Friday, 2022-November-18, around 3 AM (Eastern): promote approved build to S-4.26RC1-*, contribute to simultaneous release repo, and announce to mailing lists.

Remember to investigate and document here any failing JUnit tests.

---

• Platform:

• • Resources
• • UI
• • Debug
• • Ant
• • SWT
• • Releng

• JDT:

• • Core
• • Debug
• • UI

• PDE

• Equinox

[sravanlakkimsetti]

Go from platform releng

[sravanlakkimsetti]

notify: @jarthana @mpalat

[noopur2507]

Go from JDT UI

[jarthana]

Go from JDT Core

[SarikaSinha]

Go from
Platform

• Ant
• Debug
  JDT
• Debug

[vik-chand]

Go from PDE

Intermittent test failures are tracked by the following bugs

• org.eclipse.pde.api.tools.builder.tests.compatibility.BundleMergeSplitTests fails eclipse-pde/eclipse.pde#261
• Intermittent failures in WorkspaceModelManagerTest eclipse-pde/eclipse.pde#300
• Intermittent test failures in API tools eclipse-pde/eclipse.pde#345

[ktatavarthi]

Go from Platform UI

The test failures on Windows are captured by

• org.eclipse.core.tests.runtime.jobs.JobEventTest | testSleepOrderOfEvents fails on windows intermittently eclipse.platform#271
• JUnit tests in org.eclipse.jface.text.tests.contentassist are failing on Windows and Mac eclipse.platform.ui#890

[lshanmug]

Go from SWT
The browser test failure is tracked by - eclipse-platform/eclipse.platform.swt#103
The Browser crash issue on the new macOS 13 is tracked by eclipse-platform/eclipse.platform.swt#452. It currently looks like an Apple/Webkit issue and is being investigated by Webkit.

[iloveeclipse]

@SDawley , @akurtakov, @sravanlakkimsetti : something really strange is going on in releng.

I also saw the test fail in this bug this morning looking on RC1 build results, but now it is gone?

Do we re-publish test results with some other build results?
Can we trust the publiched RC1 test results at all?

Could be related to any of the other "strange" issues:

• Releng: Missing testManifest.xml Files #669
• No test results summary since I20221114-1800 #668

[iloveeclipse]

Looking on test XML file I see timestamp="2022-11-18T04:25:38" and ep426I-unit-win32-java11\workarea\I20221117-1330, so the test results seem to match expected RC1 build (I've checked few).

So probably "first" deployed version we saw this morning could be "just" another strange releng issue.

[SDawley]

It looks like @sravanlakkimsetti ran the ep426I-unit-win32-java11 yesterday, so collect results ran again this morning which is why you saw a change in test results for the same build.

As to why the results were different to begin with, I will have to take an in-depth look at the logs of the two builds, since the only parameter is the I-Build ID.

I'm actively looking into the missing xml files and tables and apologize for the ongoing issues.

[akurtakov]

I'm actively looking into the missing xml files and tables and apologize for the ongoing issues.

No need to apologize, as you got the ugly task :). Big parts of releng is due for rewriting as even after years with that I'm not sure which file exactly I have to edit . At some point every projects has to pay the technical debt accomodated.

[iloveeclipse]

It looks like @sravanlakkimsetti ran the ep426I-unit-win32-java11 yesterday, so collect results ran again this morning which is why you saw a change in test results for the same build.

I don't see JobEventTest in this list https://ci.eclipse.org/releng/job/AutomatedTests/job/ep426I-unit-win32-java11/34/#showFailuresLink (last Windows build), but see it in in https://ci.eclipse.org/releng/job/AutomatedTests/job/ep426I-unit-win32-java11/33/#showFailuresLink

This explains the problem with "lost" test failure.

Both builds seem to use I20221117-1330 build id, I don't see however which aggregator commit they corresponds to.

[tjwatson]

Go for Equinox

[SDawley]

Both builds seem to use I20221117-1330 build id, I don't see however which aggregator commit they corresponds to.

The last 'relevant' aggregator commit was c18c8a7, which was a fix for I20221117-1330, so there were no aggregator commits between 33 and 34.

Looking at https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/blob/master/JenkinsJobs/AutomatedTests/ep426I_unit_win32_java11.groovy it uses https://download.eclipse.org/eclipse/relengScripts/production/testScripts/hudsonBootstrap/getEBuilder.xml (which is synced via https://ci.eclipse.org/releng/job/Publish_shell_scripts_for_releng_jobs/) and that file hasnt been updated in 8 months.