Browser tests: reduce timeout for instantiation to reasonable value

The timeout for browser instantiation in the browser tests has been
increased to avoid flaky tests. However, browser instantiation taking
more than 10 seconds (the previous timeout value) is an indicator for
something being wrong with the instantiation. There is no reason why
instantiation may take that long during test execution but the same
issue should never arise in productive use, thus such a case should be
captured by tests and, if necessary, be fixed productively.

In order to do so, this change reduces the test timeout value again to a
more reasonable value.

Related to
#1676

Author: HeikoKlare

.github/workflows/maven.yml

@@ -28,10 +28,7 @@ jobs:
       matrix:
         java: [ '21' ]
         config: 
-          - { name: Linux, os: ubuntu-latest, native: gtk.linux.x86_64 }
           - { name: Windows, os: windows-latest, native: win32.win32.x86_64 }
-          - { name: MacOS x86, os: macos-13, native: cocoa.macosx.x86_64 }
-          - { name: MacOS ARM, os: macos-latest, native: cocoa.macosx.aarch64 }
     name: Verify ${{ matrix.config.name }} with Java-${{ matrix.java }}
     runs-on: ${{ matrix.config.os }}
     steps:

bundles/org.eclipse.swt/Eclipse SWT Browser/win32/org/eclipse/swt/browser/Edge.java

@@ -463,9 +463,7 @@ private static void processOSMessagesUntil(Supplier<Boolean> condition, Display
 	// The timer call also wakes up the display to avoid being stuck in display.sleep()
 	display.timerExec((int) MAXIMUM_OPERATION_TIME.toMillis(), () -> timeoutOccurred.set(true));
 	while (!display.isDisposed() && !condition.get() && !timeoutOccurred.get()) {
-		if (OS.PeekMessage(msg, 0, 0, 0, OS.PM_NOREMOVE)) {
-			display.readAndDispatch();
-		} else {
+		if (!display.readAndDispatch()) {
 			display.sleep();
 		}
 	}

tests/org.eclipse.swt.tests/JUnit Tests/org/eclipse/swt/tests/junit/AllBrowserTests.java

@@ -15,13 +15,11 @@
 
 
 import org.eclipse.test.TracingSuite;
-import org.eclipse.test.TracingSuite.TracingOptions;
 import org.junit.runner.JUnitCore;
 import org.junit.runner.RunWith;
 import org.junit.runners.Suite;
 
 @RunWith(TracingSuite.class)
-@TracingOptions(stackDumpTimeoutSeconds = 60)
 @Suite.SuiteClasses({
 	Test_org_eclipse_swt_browser_Browser.class,
 })

tests/org.eclipse.swt.tests/JUnit Tests/org/eclipse/swt/tests/junit/Test_org_eclipse_swt_browser_Browser.java

@@ -103,7 +103,7 @@
 public class Test_org_eclipse_swt_browser_Browser extends Test_org_eclipse_swt_widgets_Composite {
 
 	// TODO Reduce to reasonable value
-	private static Duration MAXIMUM_BROWSER_CREATION_TIME = Duration.ofSeconds(90);
+	private static Duration MAXIMUM_BROWSER_CREATION_TIME = Duration.ofSeconds(15);
 
 	static {
 		try {
@@ -165,10 +165,11 @@ public Test_org_eclipse_swt_browser_Browser(int swtBrowserSettings) {
 
 @BeforeClass
 public static void setupEdgeEnvironment() {
+	System.out.println("Setting up Edge environment");
 	// initialize Edge environment before any test runs to isolate environment setup
 	if (SwtTestUtil.isWindows) {
 		Shell shell = new Shell();
-		new Browser(shell, SWT.EDGE);
+		new Browser(shell, SWT.None).getUrl();
 		shell.dispose();
 	}
 }

tests/org.eclipse.swt.tests/pom.xml

@@ -25,7 +25,7 @@
   <packaging>eclipse-test-plugin</packaging>
   <properties>
     <tycho.testArgLine></tycho.testArgLine>
-    <test>AllTests</test>
+    <test>AllBrowserTests</test>
   </properties>
   <build>
     <plugins>