Community
Participate
Working Groups
With reduced threshold for UI monitoring we are seeing spurious test failures (see bug 517227). This reduction done as part of bug 566481. This aggravated spurious test failures problem. To fix this we need a way to disable UI monitoring. Need a command line option to disable UI monitoring to include it in tests.
Open this bug based on bug 566481 comment 8 @lars Can you please suggest on how to proceed?
@Lars, Can you provide the details, every other day Bug 517227 is surfacing.
(In reply to Sravan Kumar Lakkimsetti from comment #0) > To fix this we need a way to disable UI monitoring. UI monitoring can be set via preferences. IIRC I have seen JDT Debug setting preference before tests. Can this also be used here? If yes, you can use the preference spy from the e4 spies to find the correct preference store. (I can also do that, in case you don't feel comfortable with the e4 spies)
The automated tests run using ant. Its really not possible to use UI to set the preferences in the automated tests. here is the ant target that is triggered when we trigger automated tests for ant.ui bundle https://git.eclipse.org/c/platform/eclipse.platform.git/tree/ant/org.eclipse.ant.tests.ui/test.xml#n56 Please let us know how to set this preference here?
(In reply to Sravan Kumar Lakkimsetti from comment #4) > The automated tests run using ant. Its really not possible to use UI to set > the preferences in the automated tests. > > here is the ant target that is triggered when we trigger automated tests for > ant.ui bundle > > https://git.eclipse.org/c/platform/eclipse.platform.git/tree/ant/org.eclipse. > ant.tests.ui/test.xml#n56 > > Please let us know how to set this preference here? ProcessConsoleManagerTests line 100 shows an example for setting the preferences in tests.
Removing milestone from 4.19 M3 to 4.19, please re-target accordingly.
Mass move out of 4.19
Mass Move out of 4.20