Bugzilla – Full Text Bug Listing
| Summary: | [releng] Include search console automated tests in the regular tests execution | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] e4 | Reporter: | Danail Branekov <danail.branekov> | ||||
| Component: | Search | Assignee: | Bogdan Gheorghe <gheorghe> | ||||
| Status: | RESOLVED WORKSFORME | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | john.arthorne, kim.moir, ptotiger1, pwebster | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | stalebug | ||||||
| Attachments: |
|
||||||
|
Description
Danail Branekov
I've updated the feature in o.e.p.discovery.master to include the discovery_tests.feature. I've added the Orbit bundles to the test framework and have added the Search tests to our test suite. Scheduled a test build to try things out. After the discussion in bug 370631, all test fragments are converted to bundles. Bogdan, could you schedule a build to see whether this would work? Thank you! Regards, Danail The latest test results[1] show that the search console tests finished with DNF. I have found the following in the director.log[2]: >!MESSAGE Missing requirement: Search Console Utilities JUnit Test Plug-in 0.11.0.v20120209-0920 (org.eclipse.platform.discovery.util.test.unit 0.11.0.v20120209-0920) requires 'bundle org.jmock 0.0.0' but it could not be found Could you guys add org.jmock from Orbit to the test installation? Thanks! [1]http://download.eclipse.org/e4/downloads/drops/I20120209-2200/results/testResults.html [2]http://build.eclipse.org/eclipse/e4/build/e4/downloads/drops/4.0.0/I20120209-2200/eclipse-testing/results/director.log Created attachment 210912 [details]
composite test repo
It appears that when we generate the test composite, we don't have e4.targetDir replaced with the absolute path.
I think we should
1) fix /org.eclipse.e4.releng/org.eclipse.e4.builder/builder/general/tests/build.label.properties and remove that call to java, it might interfere with reading the properties.
2) The label.properties in the test dir has some information, but not e4.targetDir:
sdkResults=/shared/eclipse/e4/build/e4/downloads/drops/4.0.0/40builds/I20120210-1700/I20120210-1700
e4Results=/shared/eclipse/e4/build/e4/downloads/drops/4.0.0/I20120210-1700/I20120210-1700
buildType=I
sdkRepositoryRoot=/shared/eclipse/e4/build/e4/downloads/drops/4.0.0/targets/updates/4.2-I-builds
e4RepositoryRoot=/shared/eclipse/e4/build/e4/downloads/drops/4.0.0/targets/updates/0.12-I-builds
It seems like customTargets.xml has entries in the postBuild target to generate a label.properties, which in theory should be concatenated with the extra test properties in masterBuild.sh#runSDKTests, but it looks like the label.properties isn't even generated.
PW
This might have been premature. Looks like the build failed in part of the TM component: BUILD FAILED /shared/eclipse/e4/build/e4/org.eclipse.releng.basebuilder/plugins/org.eclipse.pde.build_3.7.0.v20110512-1320/scripts/build.xml:34: The following error occurred while executing this line: /shared/eclipse/e4/build/e4/org.eclipse.releng.basebuilder/plugins/org.eclipse.pde.build_3.7.0.v20110512-1320/scripts/build.xml:78: The following error occurred while executing this line: /shared/eclipse/e4/build/e4/gitClones/org.eclipse.e4.releng/org.eclipse.e4.builder/builder/general/customTargets.xml:18: The following error occurred while executing this line: /opt/public/eclipse/e4/build/e4/org.eclipse.releng.basebuilder_R3_7/plugins/org.eclipse.pde.build_3.7.0.v20110512-1320/templates/headless-build/allElements.xml:16: The following error occurred while executing this line: /opt/public/eclipse/e4/build/e4/org.eclipse.releng.basebuilder_R3_7/plugins/org.eclipse.pde.build_3.7.0.v20110512-1320/scripts/genericTargets.xml:56: Could not retrieve feature.xml or build.properties for feature org.eclipse.e4.tm.tests.feature. http://build.eclipse.org/eclipse/e4/logs/current.log Scheduled another build for 1430 It looks like the plugins install now (yeah!) but the framework can't find the test.xml
features/org.eclipse.platform.discovery_tests.feature/feature.xml needs to mark all of the test plugins to be unpacked (to directories instead of left as jars).
<plugin^M
id="org.eclipse.platform.discovery.ui.test.unit"^M
download-size="0"^M
install-size="0"^M
version="0.0.0"^M
unpack="false"/>^M
that should read unpack="true"
PW
Done, commit 48e36a6283f3340423dbedb64a20241cb527e60a Let's wait for the next results Kim, could you help Bogdan understand what's failing? A quick look at the latest test seems to indicate that the tests and the main plugins are all installed. and test.xml finds org.eclipse.platform.discovery.compatibility.tests_0.11.0.v20120214-1748/test.xml The current build log is at http://build.eclipse.org/eclipse/e4/logs/current.log The automated test framework we used (and a correct testComposite) are on build.eclipse.org at /shared/eclipse/e4/build/e4/downloads/drops/4.0.0/I20120214-2200/eclipse-testing When it runs it fails with: java-test: [echo] Running org.eclipse.platform.discovery.compatibility.tests.AllTests. Result file: /opt/buildhomes/e4Build/e4Tests/I20120214-2200/results/linux.gtk.x86_64/org.eclipse.platform.discovery.compatibility.tests.AllTests.xml. [java] java.lang.Exception: Could not find plugin "org.eclipse.platform.discovery.compatibility.tests" [java] at org.eclipse.test.EclipseTestRunner.loadSuiteClass(EclipseTestRunner.java:366) [java] at org.eclipse.test.EclipseTestRunner.getTest(EclipseTestRunner.java:280) [java] at org.eclipse.test.EclipseTestRunner.<init>(EclipseTestRunner.java:263) [java] at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:247) [java] at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:36) [java] at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:32) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:597) [java] at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587) [java] at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198) [java] at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) [java] at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) [java] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:352) [java] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:597) [java] at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:624) [java] at org.eclipse.equinox.launcher.Main.basicRun(Main.java:579) [java] at org.eclipse.equinox.launcher.Main.run(Main.java:1433) [java] at org.eclipse.equinox.launcher.Main.main(Main.java:1409) [java] at org.eclipse.core.launcher.Main.main(Main.java:34) [java] gogo: InterruptedException: sleep interrupted [java] java.lang.InterruptedException: sleep interrupted [java] at java.lang.Thread.sleep(Native Method) [java] at org.apache.felix.gogo.shell.Activator.run(Activator.java:72) [java] at java.lang.Thread.run(Thread.java:619) [java] Java Result: 2 PW This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. This is a mass change to close all e4 bugs marked with "stalebug" whiteboard. If this bug is still valid, please reopen and remove the "stalebug" keyword. |