Bugzilla – Full Text Bug Listing
| Summary: | Install mozilla-xulrunner190-64bit libraries on hudson slaves 1 and 2 | ||
|---|---|---|---|
| Product: | Community | Reporter: | Kim Moir <kim.moir> |
| Component: | CI-Jenkins | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | grant_gayed |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 295393 | ||
|
Description
Kim Moir
We need these libraries to run the SWT browser tests Hmm, well the installed software list sure seems to indicate that the x86_64 versions are installed as well
>rpm -qa | grep xul
mozilla-xulrunner190-1.9.0.6-1.14
mozilla-xulrunner190-32bit-1.9.0.6-1.14
And if I look at what the first package provides it lists files in /usr/lib64.
Perhaps the jobs just need to be told where to look?
-M.
I notice that we are running xulrunner 1.9.0.6 http://www.eclipse.org/swt/faq.php#browserlinux Grant should this be a problem for the SWT browser tests for 3.7 builds? I notice that there are some other bugs wrt the version of xulrunner on eclipse.org servers, see 295394 for an example. For swt/eclipse 3.7 any xulrunner version < 2.x should be fine. What if there are multiple versions on the same machine (32bit and 64bit) - how does SWT know which one to use? The xulrunner auto-detect functionalty doesn't allow us to specify the desired arch, so it does sometimes point us at a xulrunner with the wrong arch. When this happens the Browser's attempt to glue to it fails, and it falls back to trying whichever xulrunner is pointed at by the ancient MOZILLA_FIVE_HOME property. This actually often salvages this scenario because the eclipse launcher sniffs around and sets the property at eclipse start-time (if it was not already set), and it gets the arch correct more often since the launcher is recompiled for each arch. All of this being said, the safest way to ensure that this works is to just point at the xulrunner by setting the org.eclipse.swt.browser.XULRunnerPath environment variable when launching eclipse, as described in the first two paragraphs of http://www.eclipse.org/swt/faq.php#specifyxulrunner . Thanks Grant, adding export MOZILLA_FIVE_HOME=/usr/lib64/xulrunner-1.9.0.6 to my startup script for the tests allowed the SWT browser tests to run. |