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

Denis Golovin (JIRA) jira-events at lists.jboss.org
Mon Apr 15 13:24:53 EDT 2013


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

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

@[~adietish], It seems that try catch block is not really needed around UsageReport.report(), because eclipse runs all startup methods inside EarlyStartupRunnable which extends SafeRunnable. It means even if UsageReport.report() fails, exception is logged and other startup methods should not be affected.
                
> 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: Denis Golovin
>             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


More information about the jbosstools-issues mailing list