[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] UI tests on HIPP - segfaults and browser support

Hi Carsten,

I suppose that libwebkitgtk.so is not installed or otherwise not working on your HIPP. 

Eclipse would usually prefer webkitgtk over xulrunner automatically if itâs available.
By enforcing webkitgtk, you enforced a non-working configuration. 

Perhaps at least temporarily you should consider running on GTK2, by setting the SWT_GTK3 environment variable to 0:
https://www.eclipse.org/swt/faq.php#gtkstartup

Since you probably donât have shell access to you HIPP, you may have to file a Bugzilla asking Webmasterâs help to add a working version of libwebkitgtk.so to your HIPP.

Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Owner â Development Tools, Wind River
direct +43.662.457915.85  fax +43.662.457915.6
 

On 03/02/17 11:36, "cross-project-issues-dev-bounces@xxxxxxxxxxx on behalf of Carsten Reckord" <cross-project-issues-dev-bounces@xxxxxxxxxxx on behalf of reckord@xxxxxxxx> wrote:

    Hi everybody,
    
    Do any of you have UI tests running on HIPP? I'm running SWTBot tests on the MPC HIPP using Xvnc, and I'm currently having a couple of problems:
    
    1. MPC is using the embedded SWT Browser widget, and since the default XULRunner support doesn't work on GTK3, I moved my tests to WebKit (using -Dorg.eclipse.swt.browser.UseWebKitGTK=true -Dorg.eclipse.swt.browser.DefaultType=WebKit). Now I just get a very nondescript "Internal browser is not available: No more handles" SWT error the first time the browser is initialized, and all my browser-related tests (still) fail.
    
    2. I recently switched my target platform to Oxygen, and now my UI tests always segfault somewhere down the line:
    
    > # A fatal error has been detected by the Java Runtime Environment:
    > #
    > #  SIGSEGV (0xb) at pc=0x00007f19ea78b510, pid=10922, tid=0x00007f1b077af700
    > #
    > # JRE version: Java(TM) SE Runtime Environment (8.0_102-b14) (build 1.8.0_102-b14)
    > # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.102-b14 mixed mode linux-amd64 compressed oops)
    > # Problematic frame:
    > # C  [libgdk-3.so.0+0x38510]  gdk_test_simulate_button+0x0
    
    It looks like this happens the first time SWTBot "clicks" on a Link widget. But I don't have the faintest idea what to do about it.
    
    What makes this even more complicated is that I can't reproduce any of this in my own Linux VM. So any ideas how to get this solved would be greatly appreciated.
    
    /cheers
    Carsten
    
    -- 
    Yatta Solutions GmbH
    - Carsten Reckord -
    
      t  +49 (0)69 2475666-33
      f  +49 (0)69 2475668-0
      e  reckord@xxxxxxxx
      
    Anschrift Office Frankfurt a.M.
      Mainzer LandstraÃe 50
      60325 Frankfurt a.M.
    
    Anschrift Office Kassel
      UniversitÃtsplatz 12
      34127 Kassel 
      
    Sitz, Handelsregister:
      Sitz der Gesellschaft: Kassel
      Amtsgericht Kassel, HRB 14720
      USt-IdNr DE263191529
    
    GeschÃftsfÃhrung:
      Johannes Jacop
    
    Kontakt GeschÃftsstelle:
      t  +49 (0)69 2475666-0
      f  +49 (0)69 2475668-0
      e  info@xxxxxxxx
    
    _______________________________________________
    cross-project-issues-dev mailing list
    cross-project-issues-dev@xxxxxxxxxxx
    To change your delivery options, retrieve your password, or unsubscribe from this list, visit
    https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev