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

[Andre Dietisheim (JIRA)]

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

Andre Dietisheim edited comment on JBIDE-13939 at 4/15/13 12:54 PM:
--------------------------------------------------------------------

So this means we keep this as is for Alpha2 but change the way these tests are executed?

Nervertheless I'd like to get my patch applied since I found enhancements I want to get merged into upstream. I'll therefore set this issue to get fixed for Alpha2 and you're free to merge whatever patch you want. Furhtermore I'll clone it and set the fixVersion in the clone to Beta1 where I'd like to see my patch applied.
                
      was (Author: adietish):
    So this means we keep this as is for Alpha2 but change the way these tests are executed?

Nervertheless I'd like to get my patch applied since I found enhancements I want to get merged into upstream.
                  
> 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
>             Fix For: 4.1.0.Beta1
>
>
> 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