All tests of I20251024-1800 timedout

[HannesWell]

All tests of I20251024-1800:

• https://ci.eclipse.org/releng/job/AutomatedTests/job/ep438I-unit-linux-x86_64-java21/68/
• https://ci.eclipse.org/releng/job/AutomatedTests/job/ep438I-unit-linux-x86_64-java25/67/
• https://ci.eclipse.org/releng/job/AutomatedTests/job/ep438I-unit-win32-x86_64-java21/68/
• https://ci.eclipse.org/releng/job/AutomatedTests/job/ep438I-unit-macosx-aarch64-java21/68/
• https://ci.eclipse.org/releng/job/AutomatedTests/job/ep438I-unit-macosx-x86_64-java21/68/

In the logs, for example in
https://ci.eclipse.org/releng/job/AutomatedTests/job/ep438I-unit-linux-x86_64-java25/67/artifact/workarea/I20251024-1800/eclipse-testing/results/ep438I-unit-linux-x86_64-java25_linux.gtk.x86_64_25/org.eclipse.ua.tests.doc.AllTests.txt

one can find issues like:

!SESSION 2025-10-25 07:02:56.609 -----------------------------------------------
eclipse.buildId=4.38.0.I20251024-1800
java.version=25
java.vendor=Eclipse Adoptium
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments:  -application org.eclipse.test.uitestapplication formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,/home/jenkins/agent/workspace/AutomatedTests/ep438I-unit-linux-x86_64-java25/workarea/I20251024-1800/eclipse-testing/test-eclipse/eclipse/org.eclipse.ua.tests.doc.AllTests.xml -testPluginName org.eclipse.ua.tests.doc -className org.eclipse.ua.tests.doc.AllTests -timeout 7200000 -junitReportOutput /home/jenkins/agent/workspace/AutomatedTests/ep438I-unit-linux-x86_64-java25/workarea/I20251024-1800/eclipse-testing/results/ep438I-unit-linux-x86_64-java25_linux.gtk.x86_64_25
Command-line arguments:  -application org.eclipse.test.uitestapplication -data /home/jenkins/agent/workspace/AutomatedTests/ep438I-unit-linux-x86_64-java25/workarea/I20251024-1800/eclipse-testing/test-eclipse/eclipse/ui_session_sniff_folder formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,/home/jenkins/agent/workspace/AutomatedTests/ep438I-unit-linux-x86_64-java25/workarea/I20251024-1800/eclipse-testing/test-eclipse/eclipse/org.eclipse.ua.tests.doc.AllTests.xml -testPluginName org.eclipse.ua.tests.doc -className org.eclipse.ua.tests.doc.AllTests -os linux -ws gtk -arch x86_64 -consolelog -timeout 7200000 -junitReportOutput /home/jenkins/agent/workspace/AutomatedTests/ep438I-unit-linux-x86_64-java25/workarea/I20251024-1800/eclipse-testing/results/ep438I-unit-linux-x86_64-java25_linux.gtk.x86_64_25

!ENTRY org.eclipse.e4.ui.workbench3 1 0 2025-10-25 07:03:04.963
!MESSAGE starting DumpStackTracesTimer with timeout=7080000 at 2025-10-25 07:03:04 +0000

!ENTRY org.eclipse.ui 4 0 2025-10-25 07:03:05.031
!MESSAGE Unhandled event loop exception
!STACK 0
org.eclipse.swt.SWTException: Failed to execute runnable (java.util.ServiceConfigurationError: org.junit.platform.engine.TestEngine: org.junit.vintage.engine.VintageTestEngine not a subtype)
	at org.eclipse.swt.SWT.error(SWT.java:4950)
	at org.eclipse.swt.SWT.error(SWT.java:4865)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:5079)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4548)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1147)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1038)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:677)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:583)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:173)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:185)
	at org.eclipse.test.UITestApplication.run(UITestApplication.java:48)
	at org.eclipse.test.UITestApplication.start(UITestApplication.java:116)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:219)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:149)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:115)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:467)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:298)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
	at java.base/java.lang.reflect.Method.invoke(Method.java:565)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:615)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:563)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1415)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1387)
Caused by: java.util.ServiceConfigurationError: org.junit.platform.engine.TestEngine: org.junit.vintage.engine.VintageTestEngine not a subtype
	at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:559)
	at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService(ServiceLoader.java:1115)
	at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext(ServiceLoader.java:1142)
	at java.base/java.util.ServiceLoader$1.hasNext(ServiceLoader.java:1164)
	at java.base/java.util.ServiceLoader$2.hasNext(ServiceLoader.java:1246)
	at java.base/java.lang.Iterable.forEach(Iterable.java:74)
	at org.junit.platform.launcher.core.LauncherFactory.collectTestEngines(LauncherFactory.java:163)
	at org.junit.platform.launcher.core.LauncherFactory.createDefaultLauncher(LauncherFactory.java:140)
	at org.junit.platform.launcher.core.LauncherFactory.lambda$create$0(LauncherFactory.java:133)
	at org.junit.platform.launcher.core.DefaultLauncherSession.lambda$new$0(DefaultLauncherSession.java:67)
	at org.junit.platform.launcher.core.ClasspathAlignmentCheckingLauncherInterceptor.intercept(ClasspathAlignmentCheckingLauncherInterceptor.java:25)
	at org.junit.platform.launcher.core.DefaultLauncherSession.<init>(DefaultLauncherSession.java:67)
	at org.junit.platform.launcher.core.SessionPerRequestLauncher.createSession(SessionPerRequestLauncher.java:86)
	at org.junit.platform.launcher.core.SessionPerRequestLauncher.execute(SessionPerRequestLauncher.java:66)
	at org.eclipse.test.EclipseTestRunner.runTests(EclipseTestRunner.java:212)
	at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:187)
	at org.eclipse.test.UITestApplication.lambda$0(UITestApplication.java:101)
	at org.eclipse.e4.ui.internal.workbench.swt.E4Testable.lambda$1(E4Testable.java:127)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:132)
	... 24 more

[laeubi]

Related changes in jdt ui:

• Add missing version ranges to JUnit imports in MANIFEST.MF files (#1) eclipse-jdt/eclipse.jdt.ui#2562

[HannesWell]

Related changes to add missing suitably restricted version ranges in SWT and PDE:

• Add restricted version-ranges for junit-jupiter dependencies eclipse.platform.swt#2674
• Add missing upper-bound in version range of junit-jupiter dependency eclipse-pde/eclipse.pde#2061

[HannesWell]

Now that most related changes are submitted and it's hopefully already sufficient to fix the tests I restarted another I-build:

• https://ci.eclipse.org/releng/job/Builds/job/I-build-4.38/87/

Furthermore I marked tonight's build as unstable:

• https://ci.eclipse.org/releng/job/Builds/job/markBuild/1/

[HannesWell]

Now that most related changes are submitted and it's hopefully already sufficient to fix the tests I restarted another I-build:

* https://ci.eclipse.org/releng/job/Builds/job/I-build-4.38/87/

The tests are still about to time-out.
As the JDT-UI changes where not included, we maybe already got one step further. But only the logs will tell us so we have to await the timeout.

[HannesWell]

Related changes in jdt ui:

• Add missing version ranges to JUnit imports in MANIFEST.MF files (#1) eclipse-jdt/eclipse.jdt.ui#2562

Unfortunatly, this was incomplete:

• Remove unnecessary unrestricted requirements of junit-jupiter-api bundle eclipse-jdt/eclipse.jdt.ui#2568

Looks like the ordinary search with the regex-pattern junit[-.](jupiter|platform)(?!.*\[) was more reliable in this case than the AI.

[laeubi]

As the JDT-UI changes where not included, we maybe already got one step further. But only the logs will tell us so we have to await the timeout.

What bugs me a bit is why do they need to timeout and do not detect something gets wrong? One would assume if the test run fails that it even completes faster than before.

Looks like the ordinary search with the regex-pattern junit-.(?!.*[) was more reliable in this case than the AI.

Good catch, I only asked to add this to package imports but not to search for duplicate imports :-\

[laeubi]

It now looks better, the biggest bunch of failing tests is in org.eclipse.core.tests.resources now from the error reported it seems another problem of missing restrictions there:

https://download.eclipse.org/eclipse/downloads/drops4/I20251025-0900/testresults/html/org.eclipse.core.tests.resources_ep438I-unit-linux-x86_64-java21_linux.gtk.x86_64_21.html

[iloveeclipse]

See https://download.eclipse.org/eclipse/downloads/drops4/I20251025-0900/testResults.php
We have missing test results from following test suites:

• org.eclipse.jdt.ui.tests (should be addressed by Remove unnecessary unrestricted requirements of junit-jupiter-api bundle eclipse-jdt/eclipse.jdt.ui#2568)
• org.eclipse.jdt.core.tests.compiler ?
• org.eclipse.jdt.core.tests.model ?
• org.eclipse.pde.build.tests ?

[iloveeclipse]

I see that org.eclipse.jdt.core.tests.compiler & org.eclipse.jdt.core.tests.model explicitly require bundle org.junit;bundle-version="3.8.1". Is that a problem now? At least on Jenkins they seem to run.