[
https://issues.jboss.org/browse/JBIDE-13939?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-13939:
------------------------------------------
I looked into this and I found out that GlobalUsageSettingsTest is enabling usage while
testing. The correct fix is therefore IMHO to ensure this test is restoring the correct
state after each test method. I therefore implemented appropriate @Before and @After
methods for this test. The tests then succeed for me (which they're not if I run then
witout my fix).
https://github.com/jbosstools/jbosstools-base/pull/76
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