Community
Participate
Working Groups
Currently the Athena tests are not portable easily to windows system. They include a shell wrapper to launch an bash shell to start a headless display for UI tests. While this is fine, it does cause problems with a write once run anywhere design goal. Attached is a script that I used in some prior non-athena builds to run and launch tests. We would just need to tweak it so that it uses integrates with Athena, but it should be a starting point. It leverages a copy of the library.xml, and launches another eclipse headless to run ant. In order to get this working for those builds running on Hudson on build.eclipse.org, the XVNC plugin should be enabled and configured appropriately so that the build is launched in a headless display. This creates the necessary output for the tests to use if necessary. I'll attach the test.xml and the library.xml version that I use.
Created attachment 152664 [details] Library.xml used by the test.xml file
Created attachment 152665 [details] Test.xml that can be used to launch eclipse for testing. This will need tweaking to work with Athena...but might be a basis for runtTests.xml
More info on XVNC for Hudson which is already installed. http://wiki.hudson-ci.org/display/HUDSON/Xvnc+Plugin
Created attachment 152922 [details] patch to run tests in same VM as build (using same X session) This should allow builds to run their tests on Win and Mac, as well as Linux. To run in a different $DISPLAY port, wrap build w/ a Hudson job and enable the XVNC plugin so that the whole build+tests run in their own DISPLAY
Created attachment 152923 [details] mylyn/context/zip
+1 I don't see any major gotchas or anything here.
(In reply to comment #6) > +1 I don't see any major gotchas or anything here. Only gotcha that springs to mind is the one that will now require everyone to run their jobs within a VNC session. If we don't force that new behaviour, we'll have all these jobs fighting for DISPLAY=:0.0, which will cause MANY UI conflicts on build.eclipse.org If we DO force it, it'll break everyone's build until they enable that checkbox in their job's config. For now maybe we need a new build.properties option for "local tests" or "run tests with Ant" to switch over to the new way; later we can make that the default behaviour. I can make it default for Win / Mac - I'm just concerned about Linux builds.
(In reply to comment #7) > (In reply to comment #6) > > +1 I don't see any major gotchas or anything here. > > Only gotcha that springs to mind is the one that will now require everyone to > run their jobs within a VNC session. > > If we don't force that new behaviour, we'll have all these jobs fighting for > DISPLAY=:0.0, which will cause MANY UI conflicts on build.eclipse.org > > If we DO force it, it'll break everyone's build until they enable that checkbox > in their job's config. > > For now maybe we need a new build.properties option for "local tests" or "run > tests with Ant" to switch over to the new way; later we can make that the > default behaviour. > > I can make it default for Win / Mac - I'm just concerned about Linux builds. Yeah, you'll want to grandfarther this in... with a notice to all athena build users that the old way is being deprecated and will be removed. I have no problem with a property that is set like: runAntTests, and have that set to true or 1. Otherwise it just runs the old tests method. Plus this gives us a way to experiment with it and work out any final kinks in the production system.
Created attachment 153209 [details] new patch patch to set default incubation=(nullstring) also sets new default build.steps=testLocal for running tests in Ant (win/mac/lin) instead of now-deprecated build.steps=test, which launches a separate xvnc/xvfb thread for the tests. Old way still works so as to ease adoption of Hudson users
Last patch checked into CVS and released onto build.eclipse.org. Documentation: http://wiki.eclipse.org/Common_Build_Infrastructure/Testing Reopen if anyone's broken by this.
*** Bug 268420 has been marked as a duplicate of this bug. ***
(In reply to comment #11) > *** Bug 268420 has been marked as a duplicate of this bug. *** Managed to build GEF - and run UI tests! - on WinXPHome with VirtualBox 3.0.10 Mac OSX Server 10.5.6 is not playing nicely - perhaps I'm getting the wrong ws value (carbon vs. cocoa) ?
great job guys! Old bash script for testing was so scaring. btw. Nick, how are people supposed to know about depraciated things, like build.steps=test?
Not sure if this is a build.eclipse.org, problem or not, but using testLocal, with XVNC enabled seems to not have the test ever complete. Normally it takes about a minute and half to run the actual tests for PsychoPath, but it seems to be stuck as it's been sitting there for about 10 minutes on the test job. Here is the last lines of the console output: [build] init: [build] [build] suite: [build] [build] init: [build] [mkdir] Created dir: /opt/users/hudsonbuild/.hudson/jobs/cbi-wtp-wst.xsl.psychopath/workspace/build/athena/testing/target/eclipse/results [build] [build] ui-test: [build] [build] java-test: [build] [echo] Running org.eclipse.wst.xml.xpath2.processor.test.AllPsychoPathTests. Result file: /opt/users/hudsonbuild/.hudson/jobs/cbi-wtp-wst.xsl.psychopath/workspace/build/athena/testing/target/eclipse/results/org.eclipse.wst.xml.xpath2.processor.test.AllPsychoPathTests.xml. I ended up killing the job after an hour and 10 minutes. Job normally completes between 20 and 35 minutes depending on how slow CVS is on checkouts.
(In reply to comment #13) > great job guys! Old bash script for testing was so scaring. > > btw. Nick, > how are people supposed to know about depraciated things, like > build.steps=test? People like yourself add things to the FAQ or elsewhere in the wiki that I've forgotten to document? *shrug* :) > [build] java-test: > [build] [echo] Running > org.eclipse.wst.xml.xpath2.processor.test.AllPsychoPathTests. Result file: > /opt/users/hudsonbuild/.hudson/jobs/cbi-wtp-wst.xsl.psychopath/workspace/build/athena/testing/target/eclipse/results/org.eclipse.wst.xml.xpath2.processor.test.AllPsychoPathTests.xml. > > I ended up killing the job after an hour and 10 minutes. Job normally > completes between 20 and 35 minutes depending on how slow CVS is on checkouts. Sounds a little like what I was getting on Mac OSX 10.5.7 last night... a TON of errors dumped to console... see bug 268420.
(In reply to comment #15) > Sounds a little like what I was getting on Mac OSX 10.5.7 last night... a TON > of errors dumped to console... see bug 268420. I think we need to set the path to XVNC correctly in the configuration file. For some reason I'm getting 404 errors when I click the expanded help for the Xvnc plugin on build eclipse.org. I'll look at bug 268420 as well. Any idea what the correct path for xvnc is on the build machine?
> (In reply to comment #16) > Any idea what the correct path for xvnc is on the build machine? /usr/X11R6/bin/Xvnc is what $ which Xvnc gives me.
