Community
Participate
Working Groups
In a lot of our test scripts, we have set (hard coded) MOZILLA_FIVE_HOME. Such as for linux: MOZILLA_FIVE_HOME=/usr/lib/xulrunner-1.9.0.19 I was under the impression this should no longer be needed, right? I don't know if it "harms" anything ... but ... seems like it _might_, so would like to know a) if its needed b) what value should it have. On build.eclipse.org, I do see defined: /usr/lib/xulrunner-1.9.1 -> xulrunner-1.9.1.19 So ... can I get rid of it? Or should I fix the value to be accurate to what's available? Would this inaccuracy be "hurting" anything? Causing slowness?
Bogdan, can you answer this question, please?
I should say, the value of /usr/lib/xulrunner-1.9.1 -> xulrunner-1.9.1.19 is just from the build machine, I guess each Hudson slave we test on may or may not have that version, may not have one at all, etc., So, I'd prefer to get rid of if its not needed ... or, understand what we do need so we can be sure to test if the hudson slave has it, get them set up how we need, or what ever.
I've removed for the case we run on eclipse.org. testAll.sh - org.eclipse.releng.eclipsebuilder/eclipse/buildConfigs/sdk.tests/testConfigs/linux (4 matches) But left in for these we do not run ... but, pretty sure no longer required for any platform with a relatively normal install configuration. testAll.sh - org.eclipse.releng.eclipsebuilder/eclipse/buildConfigs/sdk.tests/testConfigs/rhelws5-6.0 (3 matches) testAll.sh - org.eclipse.releng.eclipsebuilder/eclipse/buildConfigs/sdk.tests/testConfigs/rhelws5-perf (3 matches) testAll.sh - org.eclipse.releng.eclipsebuilder/eclipse/buildConfigs/sdk.tests/testConfigs/sled10-perf (3 matches)
In case it helps, I regularly install the latest firefox on build.eclipse.org. I don't know if this folder is available to Hudson windows slave though: johna@build:/shared/common> cd firefox- firefox-10.0/ firefox-4.0/ firefox-6.0/ firefox-9.0.1/ firefox-11.0/ firefox-4.0b11/ firefox-7.0.1/ firefox-3.6.13/ firefox-5.0/ firefox-8.0.1/
If the test machine has xulrunner-1.9.0.x then MOZILLA_FIVE_HOME should not be set (assuming the XULRunner is registered and therefore discoverable, which should be the case by default).
So, sounds like my request to webmasters should be to "install the latests firefox (currently 12, though 11 would work) or install xulrunner > xulrunner-1.9.0.x which ever is easiest for them".
And ... assume this is independent of "run Xvnc" setting in Hudson? I _think_ I have that set for Linux jobs (or, all UI tests would fail) but I'll double check. And, assume independent of version of Xvnc and its configuration?
Installing a newer Firefox will not change anything, the Browser will not attempt to use it. The current installation of XULRunner 1.9.0.x should be fine, this is a supported version. If a newer one gets installed then its version must be earlier than 4.
(In reply to comment #8) > Installing a newer Firefox will not change anything, the Browser will not > attempt to use it. > Thanks for clarifying. > The current installation of XULRunner 1.9.0.x should be fine, this is a > supported version. Well, we do not know that is installed on each of the Hudson slave machines (just the build machine, which is not running the tests) so the point is to give a specification for the Hudson slave machines. > If a newer one gets installed then its version must be earlier than 4. Ok, to be explicit this means XULRunner greater than or equal to 1.9.0.19 but less than 1.9.4.0, right? And, I'll mention "XULRunner should be registered and discovered" which should be the default if installed through the normal mechanisms. (Is there some way administrator can tell if registered, from a command line? They might know ... but, if we can spell it out, that would be helpful).
I've opened bug 379018. You can monitor or give more details there.
