[Linux] Fix random test failures of browser tests #1523

Browser tests randomly fail during Jenkins execution because of too many
opened file descriptors. The reason seems to be that the build uses
parallel execution and Maven plugins executed for other bundles may have
opened and closed file descriptors in parallel, which are erroneously
taken into account by the browser tests evaluating the number of file
descriptors left open after a test execution.

This change excludes open file descriptors for Maven artifacts used in
parallel by other Maven plugins by not considering file descriptors with
their path containing ".m2".

Fixes #1523

Author: HeikoKlare

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

@@ -2846,7 +2846,13 @@ private static List<String> getOpenedDescriptors() {
 	try(DirectoryStream<Path> directoryStream = Files.newDirectoryStream(fd)){
 		directoryStream.forEach(f -> {
 			try {
-				paths.add(Files.isSymbolicLink(f)? Files.readSymbolicLink(f).toString() : f.toString());
+				// Do not consider file descriptors of Maven artifacts that are currently opened
+				// by other Maven plugins executed in parallel build (such as parallel
+				// compilation of the swt.tools bundle etc.)
+				String resolvedPath = Files.isSymbolicLink(f) ? Files.readSymbolicLink(f).toString() : f.toString();
+				if (!resolvedPath.contains(".m2")) {
+					paths.add(resolvedPath);
+				}
 			} catch (IOException e) {
 				e.printStackTrace();
 			}