Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suppress Windows Defender Autofix startup check in test-runtimes part 2 #1686

Conversation

HannesWell
Copy link
Member

Consider also applications specified on the CLI via the '-application' argument when determining the actually running application. Otherwise always the application defined in the product definition is assumed.

Fixes #1683

Consider also applications specified on the CLI via the '-application'
argument when determining the actually running application. Otherwise
always the application defined in the product definition is assumed.

Fixes eclipse-platform#1683
Comment on lines +116 to +125
private static String getRunningApplicationId() {
@SuppressWarnings("restriction")
String appId = System.getProperty(org.eclipse.core.internal.runtime.InternalPlatform.PROP_APPLICATION);
if (appId != null) {
return appId;
}
IProduct product = Platform.getProduct();
return product != null ? product.getApplication() : null;
}

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reading the System-properties is effectively what's done in the proposed solution in #1453 (comment) (EnvironmentInfo only also considers a potential SecurityManager before reading the System-properties, but I assume that nobody is using SecurityManagers anymore).
It is set at startup in org.eclipse.equinox.internal.app.CommandLineArgs class.

On the long run it might be interesting to have something like this available as API, e.g. Platform.getApplication() similar to Platform.getProduct() since this might be of interest for others as well.

Copy link
Contributor

Test Results

   612 files   -   306     612 suites   - 306   59m 18s ⏱️ - 10m 37s
 7 434 tests ±    0   7 279 ✅  -     4  155 💤 +  5  0 ❌  - 1 
15 634 runs   - 7 817  15 287 ✅  - 7 661  347 💤  - 155  0 ❌  - 1 

Results for commit 76f9f43. ± Comparison against base commit 42a4d8b.

This pull request skips 5 tests.
org.eclipse.ui.genericeditor.tests.HoverTest ‑ testEnabledWhenHover
org.eclipse.ui.genericeditor.tests.HoverTest ‑ testMultipleHover
org.eclipse.ui.genericeditor.tests.HoverTest ‑ testProblemHover
org.eclipse.ui.genericeditor.tests.HoverTest ‑ testSingleHover
org.eclipse.ui.genericeditor.tests.ShowInformationTest ‑ testInformationControl

@HannesWell
Copy link
Member Author

API tools failure in Linux-build seems unrelated.

Submitting.

@HannesWell HannesWell merged commit fc59f24 into eclipse-platform:master Feb 15, 2024
15 of 16 checks passed
@HannesWell HannesWell deleted the windows-defender-testRuntime-fix2 branch February 15, 2024 09:47
@iloveeclipse
Copy link
Member

@HannesWell : if you are ready, please trigger new IBuild, as we need Windows tests for M3 running and we also want have new build for eclipse-jdt/eclipse.jdt.core#2025.

@HannesWell
Copy link
Member Author

@iloveeclipse could you please start an I build, I'm not at my computer anymore.
I can verify the result this evening.

@iloveeclipse
Copy link
Member

OK, started https://ci.eclipse.org/releng/job/Builds/job/I-build-4.31/137/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Win] Most tests in I20240213-1800 DNF waiting on "WindowsDefenderConfigurator"
2 participants