Community
Participate
Working Groups
As far as I can see Orion is being tested with a version of Chrome, 12, that no one is using. The current stable version is 14, the beta is 15. Even two months ago, 77% of Chrome users were on 13. By now most are upgrading to 14. 12 is like so over ;-) And I can tell you that Orion does work properly on 15 or 16.
I'm going to add Chrome 14 and FireFox 7. browsers are releasing too often for us to keep up with beta channels as well.
The stable version is 15: http://googlechromereleases.blogspot.com/ The Google Chrome team is happy to announce the arrival of Chrome 15.0.874.102 to the Stable Channel for Windows, Mac, Linux, and Chrome Frame. Since the browsers run on a 6 week cycle and Orion on a 12 week cycle, consider testing Orion with the beta version at the beginning of its cycle. That way at the end of the Orion cycle, the Chrome version it was tested with will be the stable version.
Sigh.. when I started working this on Monday, Chrome 14 was the latest. I am having trouble getting Chrome 14 running so maybe I will try going straight to Chrome 15.
Chrome is now at v18 and Orion testing as at v12.
I can't figure out how to install newer Chrome versions without using RPM. Our build machine is a multi-user SUSE Linux install that I don't have root privileges on. Our previous build-meister got it running by cobbling together libraries from various places until it started working, but I have tried this with Chrome 15 and not succeeded yet. This link gives a sampling of what needs to be done but the specific libraries depend on the Chrome version and your particular distro: http://unix.stackexchange.com/questions/8926/installing-chrome-on-linux-without-needing-to-be-root I do need to install FF 9 though which I will do shortly.
I've asked as a user: http://www.google.com/support/forum/p/Chrome/thread?tid=6c89844b938390b7&hl=en
Apparently Chrome cannot be installed on linux without admin privs.
Or maybe this is a hint: ---- perhaps you could unpack the package manually. Not sure what the sandbox will do then. The command would be something like "dpkg-deb -x googel-chrome-whatever.deb". See man dpkg-deb for more. ---
Thanks for looking into it. It can be manually extracted, but it won't run because it has libraries missing. I guess we'll need to get an admin install on the build machine to make sure we're testing the real thing.
Well, I found the root of our problem: http://code.google.com/p/chromium/issues/detail?id=93054 Chrome after version 12 is not support on SUSE Linux Enterprise Server. Period. This is the build machine distro used by eclipse.org, and one of the most common enterprise linux distros. Yay Chrome. If we want to continue testing Chrome it sounds like we'll need a test machine outside eclipse.org.
Changing title because Firefox is not a problem.
C:\Users\kmoir\AppData\Local\Google\Chrome\Application\chrome.exe That is the path of Chrome on the Hudson windows machine. I have updated it to Chrome 23.
http://git.eclipse.org/c/orion/org.eclipse.orion.server.git/commit/?id=52f1eb9be181200ea2ad73b2ede08a0bcd157111
We are now running automated tests on Chrome 23 Windows as of I20121206. http://download.eclipse.org/orion/drops/I201212061505/index.html
