[jira] Updated: (HARMONY-5306) [buildtest][EUT] swt suite intermittently crashes by timeout

["Ilya Berezhniuk (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HARMONY-5306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ilya Berezhniuk updated HARMONY-5306:
-------------------------------------

    Attachment: eut.3.3.swt.patching.zip

I've prepared patches and script for patching EUT 3.3 to pass swt suite.
(See "eut.3.3.swt.patching" in the attached archive.)

This script is similar to scripts for patching EUT 3.2.
To perform needed URL substitutions 'swt.local.url' property in 'properties' file should be set to locally available  URL.
Default value of 'swt.local.url' is 'http://www.googl.com'.

I've just started testing with patched EUTs, so I'm not quite sure that all is OK.
Probably Test_org_eclipse_swt_browser_Browser.java test should not be patched - I did not check this.
But all other changes are certainly reasonable.


BTW, I've checked EUT 3.3 on my home machine (w/o proxy); 'swt' suite has passed 10 times without hangs.


> [buildtest][EUT] swt suite intermittently crashes by timeout
> ------------------------------------------------------------
>
>                 Key: HARMONY-5306
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5306
>             Project: Harmony
>          Issue Type: Bug
>          Components: build - test - ci
>    Affects Versions: 5.0M4
>         Environment: Linux/x86
>            Reporter: Ilya Berezhniuk
>         Attachments: eut.3.3.swt.patching.zip
>
>
> Cruise control results show crash in 'swt' suite from time to time. The latest result:
> http://people.apache.org/~smishura/r603433/Linux_x86/eut33/
> I've detected that this crash is actually killing swt suite by timeout.
> Checking 'swt' from Eclipse GUI shows that the problem is in message window waiting for button pressing.
> This message box shows the following message:
> "The operation timed out when attempting to contact www.google.com."
> I can reproduce this problem on Sun and BEA VMs too.
> So I think the problem is in problems with network on particular host.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.