Community
Participate
Working Groups
Unit tests are currently broken. 1) Tests are not even running because of an incorrect path copying the archive over to use for testing. 2) I have no idea where the test results page content is coming from, but it isn't real. (http://download.eclipse.org/e4/sdk/drops/I20110210-2002/testResults.php)
problem 3: We are currently properly installing the test bundle into the eclipse-to-be-tested using the p2 director. However the org.eclipse.test_3.3.0 that we are using assumes that it is installed into dropins. Version 3.3.100 does the right thing, we need to use that instead.
(CCing Kim & Dani as a FYI) Some 3.7 unit tests will run tonight on the 4.1 SDK. This is linux.gtk.x86_64 using Sun 1.6. Tests from the 3.7 SDK: org.eclipse.ant.tests.core org.eclipse.ant.tests.ui org.eclipse.debug.tests org.eclipse.jdt.text.tests org.eclipse.jdt.compiler.apt.tests org.eclipse.jdt.ui.tests org.eclipse.jface.text.tests org.eclipse.pde.ui.tests org.eclipse.text.tests e4 Tests: org.eclipse.e4.ui.tests.css.swt org.eclipse.e4.ui.tests.css.core org.eclipse.e4.ui.tests org.eclipse.e4.core.tests.services org.eclipse.e4.core.tests In test builds there were problems with out of Memory permgen errors. The tests are now being run with -XX:MaxPermSize=256m. Note that these tests run ok against the 3.7 SDK without requiring the increased permgen size. As an implementation detail, to avoid problems similar to bug 335723, tests are being run under the build user home directory which is a faster disk than /shared according to http://wiki.eclipse.org/images/1/1f/Build_infra_layout.png. The test results HTML page is still a work in progress, and may not be ready for tonight
Even though the summary HTML results won't be ready, individual suite results should be available under urls like http://download.eclipse.org/e4/sdk/drops/<build-id>/results/html/<testbundle>_linux.gtk.x86_64.html
(In reply to comment #3) > Even though the summary HTML results won't be ready, individual suite results > should be available under urls like > http://download.eclipse.org/e4/sdk/drops/<build-id>/results/html/<testbundle>_linux.gtk.x86_64.html Andrew, that directory doesn't appear to be available in http://download.eclipse.org/e4/sdk/drops/I20110218-0831 PW
(In reply to comment #4) > (In reply to comment #3) > > Even though the summary HTML results won't be ready, individual suite results > > should be available under urls like > > http://download.eclipse.org/e4/sdk/drops/<build-id>/results/html/<testbundle>_linux.gtk.x86_64.html > > Andrew, that directory doesn't appear to be available in > http://download.eclipse.org/e4/sdk/drops/I20110218-0831 > > PW I released a change last night around 18:30 accidentally commenting out the actual executing the tests. I ended up rerunning them manually this morning and copying the results over. I have fixed the mistake and the next build should be better. There are still some issues remaining: - links in the build pages aren't all quite right - there are no results for the e4 tests here:http://download.eclipse.org/e4/sdk/drops/I20110218-0831/results/testResults.html, have to figure out why. - I want to update the build emails to show test results similar to http://dev.eclipse.org/mhonarc/lists/orion-dev/msg00178.html so that developers are more aware of failures.
I tried running the tests but they died while running org.eclipse.update.tests.core. Did we remove the org.eclipse.update.core stuff from the 4.x build because it's deprecated and has been replaced by p2? This seems to be the case based on bug 316008 comment 0.
I think the releng tests are refusing to run for the same reasons. Cannot complete the install because one or more required items could not be found. Software being installed: Eclipse Releng Tests 3.2.100.v20110215-0800 (org.eclipse.releng.tests 3.2.100.v20110215-0800) Missing requirement: Versioning Tools Plug-in 1.0.0 (org.eclipse.pde.tools.versioning 1.0.0) requires 'package org.eclipse.update.core 0.0.0' but it could not be found
Marking this fixed. Test results should now be showing up in the build result email. Any outstanding issues should be raised as a new bug.
