Community
Participate
Working Groups
Error reporting does not provide the cause for a failed test execution. For example, when launching a JUnit Plug-in test suite (via ASF) without a valid Workbench Location, a InactiveProcessException exception is thrown: [tptp:execution] adding file BVT/AllBVTJUnitPluginTests.testsuite [tptp:execution] Test started! [tptp:execution] Test 'BVT/AllBVTJUnitPluginTests.testsuite' executing [tptp:execution] org.eclipse.hyades.internal.execution.local.control.InactiveProcessException [tptp:execution] at org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub.launch(TestExecutionHarnessExecutorStub.java:422) [tptp:execution] at org.eclipse.hyades.execution.harness.TestExecutionHarness.launchTestExecution(TestExecutionHarness.java:2098) [tptp:execution] at org.eclipse.hyades.execution.harness.TestExecutionHarness.access$2(TestExecutionHarness.java:1830) [tptp:execution] at org.eclipse.hyades.execution.harness.TestExecutionHarness$2.run(TestExecutionHarness.java:750) [tptp:execution] at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) [tptp:execution] java.lang.RuntimeException: org.eclipse.hyades.internal.execution.local.control.InactiveProcessException [tptp:execution] at org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub.handleException(TestExecutionHarnessExecutorStub.java:347) [tptp:execution] at org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub.launch(TestExecutionHarnessExecutorStub.java:434) [tptp:execution] at org.eclipse.hyades.execution.harness.TestExecutionHarness.launchTestExecution(TestExecutionHarness.java:2098) [tptp:execution] at org.eclipse.hyades.execution.harness.TestExecutionHarness.access$2(TestExecutionHarness.java:1830) [tptp:execution] at org.eclipse.hyades.execution.harness.TestExecutionHarness$2.run(TestExecutionHarness.java:750) [tptp:execution] at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) [tptp:execution] Caused by: org.eclipse.hyades.internal.execution.local.control.InactiveProcessException [tptp:execution] at org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub.launch(TestExecutionHarnessExecutorStub.java:422) [tptp:execution] ... 4 more [tptp:execution] org.eclipse.core.runtime.CoreException: IWAT4039E The Test Execution Harness reported the following problems:org.eclipse.hyades.internal.execution.local.control.InactiveProcessException [tptp:execution] at org.eclipse.hyades.test.core.launch.delegates.AbstractLaunchConfigurationDelegate2.launch(AbstractLaunchConfigurationDelegate2.java:195) [tptp:execution] at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:764) [tptp:execution] at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:614) [tptp:execution] at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:607) [tptp:execution] at org.eclipse.hyades.test.core.services.AbstractTestExecutionService.launch(AbstractTestExecutionService.java:797) [tptp:execution] at org.eclipse.hyades.test.core.services.AbstractTestExecutionService.execute(AbstractTestExecutionService.java:585) [tptp:execution] at org.eclipse.hyades.automation.server.AbstractService.execute(AbstractService.java:43) [tptp:execution] at org.eclipse.hyades.automation.server.ServiceProxy$1.run(ServiceProxy.java:141) [tptp:execution] at org.eclipse.hyades.automation.core.utils.ReusableThread.run(ReusableThread.java:131) [tptp:execution] at java.lang.Thread.run(Thread.java:801) BUILD FAILED /home/build/BVT/scripts/build.xml:28: java.lang.NullPointerException The test runner should do a better job at capturing the root cause of the failed test execution and reporting it back to the test harness.
In addition, when test runners launch Eclipse applications, the fatal errors recorded in the .log file should be captured and returned to the user.
*** Bug 211091 has been marked as a duplicate of this bug. ***
Deferring to future as approved by the TPTP PMC (http://dev.eclipse.org/mhonarc/lists/tptp-pmc/msg04926.html).
*** This bug has been marked as a duplicate of bug 178595 ***
Closing.
