harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Berezhniuk (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-5306) [buildtest][EUT] swt suite intermittently crashes by timeout
Date Fri, 14 Dec 2007 21:43:43 GMT

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

Ilya Berezhniuk commented on HARMONY-5306:

I've prepared a script to patch EUT tests.
It changes www.google.com in Browser1 and Browser6 tests onto some locally available URL provided
in script parameters.
This script is made from scripts for EUT 3.2 in eut/extra dir.

When I tried these patched tests, I've got the suite passed more often, but sometimes it still
hangs in batch run.
When I started batch run with display set to Xserver on local machine, I've observed that
Browser3 test is also hanged with "google" error.
It appeared that test HTML for Browser3 to open in new window also contains www.google.com.

I think I'll update the script for patching EUT soon and lay it to JIRA.

> [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
> 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.

View raw message