[jbosstools-issues] [JBoss JIRA] (JBIDE-13939) Usage tests freeze on Kepler M6

[Denis Golovin (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-13939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766912#comment-12766912 ] 

Denis Golovin commented on JBIDE-13939:
---------------------------------------

If this test is not testing UI then it should be executed as core test, it works for me
{code}
### Eclipse Workspace Patch 1.0
#P org.jboss.tools.usage.test
diff --git pom.xml pom.xml
index 1630204..dd2e299 100644
--- pom.xml
+++ pom.xml
@@ -15,4 +15,18 @@
 		<coverage.filter>org.jboss.tools.usage*</coverage.filter>
 		<emma.instrument.bundles>org.jboss.tools.usage</emma.instrument.bundles>
 	</properties>
+	
+	<build>
+		<plugins>
+			<plugin>
+				<groupId>org.eclipse.tycho</groupId>
+				<artifactId>tycho-surefire-plugin</artifactId>
+				<version>${tychoVersion}</version>
+				<configuration>
+					<useUIHarness>false</useUIHarness>
+					<useUIThread>false</useUIThread>
+				</configuration>
+			</plugin>
+		</plugins>
+	</build>
 </project>
{code}
                
> Usage tests freeze on Kepler M6
> -------------------------------
>
>                 Key: JBIDE-13939
>                 URL: https://issues.jboss.org/browse/JBIDE-13939
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: usage
>    Affects Versions: 4.1.0.Alpha1, 4.1.0.Alpha2
>            Reporter: Snjezana Peco
>            Assignee: Snjezana Peco
>
> The usage tests freezes because they are executed before calling the UsageReportEnablementDialog dialog.
> They set the "usage_reporting_enabled" property to true which enables opening the UsageReportEnablementDialog dialog.
> The fix is to set usage_reporting_enabled=false after the latest test (UsageIntegrationTest).
> The issue happens on Kepler M6. I suppose it is caused by some changes related to the handling UI messagess/jobs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira