Remove formatter parameter in EclipseTestRunner

[akurtakov]

The value was simply ignored and it was hiding the test-output parameter setting due to convoluted handling..

[akurtakov]

@HannesWell Would you please test that this one works as expected?

[eclipse-platform-bot]

This pull request changes some projects for the first time in this development cycle.
Therefore the following files need a version increment:

eclipse.platform.releng/bundles/org.eclipse.test/META-INF/MANIFEST.MF

An additional commit containing all the necessary changes was pushed to the top of this PR's branch. To obtain these changes (for example if you want to push more changes) either fetch from your fork or apply the git patch.

Git patch

From c513fee1380360f1b68c907e0252f200339152b0 Mon Sep 17 00:00:00 2001
From: Eclipse Platform Bot <platform-bot@eclipse.org>
Date: Wed, 17 Jun 2026 06:19:35 +0000
Subject: [PATCH] Version bump(s) for 4.41 stream


diff --git a/eclipse.platform.releng/bundles/org.eclipse.test/META-INF/MANIFEST.MF b/eclipse.platform.releng/bundles/org.eclipse.test/META-INF/MANIFEST.MF
index 4ed0ed4c8b..2dec633048 100644
--- a/eclipse.platform.releng/bundles/org.eclipse.test/META-INF/MANIFEST.MF
+++ b/eclipse.platform.releng/bundles/org.eclipse.test/META-INF/MANIFEST.MF
@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: %pluginName
 Bundle-SymbolicName: org.eclipse.test; singleton:=true
-Bundle-Version: 3.6.600.qualifier
+Bundle-Version: 3.6.700.qualifier
 Eclipse-BundleShape: dir
 Bundle-Vendor: %providerName
 Bundle-Localization: plugin
-- 
2.54.0

Further information are available in Common Build Issues - Missing version increments.

[HannesWell]

@HannesWell Would you please test that this one works as expected?

Yes, I can do that tomorrow, but it's currently not easy as one first has to produce a new unofficial I-build in a side location and make the test use it. But it's doable.

Do you have a specific test-suite in mind to run with this?

[akurtakov]

Nothing specific. I'm interested that tests still run and unit tests reports do not change - so probably a full build would be best.