Community
Participate
Working Groups
Created attachment 92285 [details] eclipse .log Build ID: I20080207-1530 Steps To Reproduce: 1. Install tptp.runtime.allInOne-4.5.0M5 (on Win XP SP2) 2. Install cosmos-sdk-incubation-COSMOS-1.0.0-200802131535 3. Checkout org.eclipse.cosmos/tests/data-collection/org.eclipse.cosmos.dc.cmdbf.services.tests from dev.eclipse.org, /cvsroot/technology 4. Right click any testsuite (eg: TestQueryInputTransformer.testsuite) in junits folder 5. Runs as -> Test 6. Hangs at 36% and fails with the error: IWAT4039E The Test Execution Harness reported the following problems:org.eclipse.hyades.internal.execution.local.control.InactiveProcessException More information: Tried with both Sun & IBM java 1.5. Eclipse log is attached. Also tried cleaning and refreshing the workspace and restarting eclipse/OS. But the junit can be executed successfully by right clicking and running the .java file in src folder.
I can reproduce this symptom. I am investigating the root cause. I noticed that the org.eclipse.cosmos.dc.cmdbf.services.tests plug-in does not compile. Can you fix these errors? How did you create the TestQueryInputTransformer.testsuite test suite (and others)? Did you create them from scratch or import existing JUnit test classes?
org.eclipse.cosmos.dc.cmdbf.services.tests plug-in has a dependency on org.eclipse.cosmos.common.tests. Please checkout the same from org.eclipse.cosmos/tests/common in same repository You can ignore the single error - Plug-ins declaring extensions or extension points must set the singleton directive to true I didn't create them, they were created and is being used by the component team. If you want more info I can ask them and find out. But as far as I know, they don't have any issues and use this for the FVT.
Created attachment 92677 [details] eclipse.log tptp 4,4,1
I tried with the latest TPTP public release (4.4.1), but still the same error (tptp.runtime.allInOne.win32.win32.x86-TPTP-4.4.1). Attached the eclipse.log for the same.
Hi, I posted the following note to your newsgroup post and to tptp-testing-tools-dev mailing list after getting the email from Sheldon: In general, the InactiveProcessException means that the session JVM kicked off the test runner java process, which then immediately died. Typically, this problem is due to missing items in the classpath for the test to execute such that the runner failed to start. I have existing defects to improve the error messages to the user. I will try to help more with this if you convinced the classpath is complete. DuWayne
Deferring to I7 as discussed by PMC/AG (http://wiki.eclipse.org/TPTP-AG-20080331#Test_Project).
I was experimenting with different configurations and combination and found out the following: While running the TPTP automation framework client I got the following error: E:\Bobz\workarea\tptp.runtime.allInOne.win32.win32.x86-TPTP-4.4.1\eclipse\plugin s\org.eclipse.hyades.execution_4.4.100.v200802221314>java -cp ./bin;tptp-automat ion-client.jar org.eclipse.hyades.automation.client.adapters.shell.AutomationCli entAdapter -configfile cosmos.config Test started! Test 'junits/TestQueryInputTransformer.testsuite' executing org.eclipse.hyades.internal.execution.local.control.InactiveProcessException at org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub .launch(TestExecutionHarnessExecutorStub.java:422) at org.eclipse.hyades.execution.harness.TestExecutionHarness.launchTestE xecution(TestExecutionHarness.java:2098) at org.eclipse.hyades.execution.harness.TestExecutionHarness.access$2(Te stExecutionHarness.java:1830) at org.eclipse.hyades.execution.harness.TestExecutionHarness$2.run(TestE xecutionHarness.java:750) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) java.lang.RuntimeException: org.eclipse.hyades.internal.execution.local.control. InactiveProcessException at org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub .handleException(TestExecutionHarnessExecutorStub.java:347) at org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub .launch(TestExecutionHarnessExecutorStub.java:434) at org.eclipse.hyades.execution.harness.TestExecutionHarness.launchTestE xecution(TestExecutionHarness.java:2098) at org.eclipse.hyades.execution.harness.TestExecutionHarness.access$2(Te stExecutionHarness.java:1830) at org.eclipse.hyades.execution.harness.TestExecutionHarness$2.run(TestE xecutionHarness.java:750) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: org.eclipse.hyades.internal.execution.local.control.InactiveProcessEx ception at org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub .launch(TestExecutionHarnessExecutorStub.java:422) ... 4 more org.eclipse.core.runtime.CoreException: IWAT4039E The Test Execution Harness rep orted the following problems:org.eclipse.hyades.internal.execution.local.control .InactiveProcessException at org.eclipse.hyades.test.core.launch.delegates.AbstractLaunchConfigura tionDelegate2.launch(AbstractLaunchConfigurationDelegate2.java:195) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConf iguration.java:759) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConf iguration.java:608) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConf iguration.java:601) at org.eclipse.hyades.test.core.services.AbstractTestExecutionService.la unch(AbstractTestExecutionService.java:795) at org.eclipse.hyades.test.core.services.AbstractTestExecutionService.ex ecute(AbstractTestExecutionService.java:583) at org.eclipse.hyades.automation.server.AbstractService.execute(Abstract Service.java:43) at org.eclipse.hyades.automation.server.ServiceProxy$1.run(ServiceProxy. java:141) at org.eclipse.hyades.automation.core.utils.ReusableThread.run(ReusableT hread.java:131) at java.lang.Thread.run(Thread.java:810) Eventhough the interal RAC(ACServer.exe) is started, it crashes due to some reason and hence the above error - InactiveProcessException I tried the same command again, after starting an external RAC as follows agntctrl.win_ia32-TPTP-4.5.0M5\bin>ACServer.exe E:\Bobz\workarea\tptp.runtime.allInOne.win32.win32.x86-TPTP-4.4.1\eclipse\plugin s\org.eclipse.hyades.execution_4.4.100.v200802221314>java -cp ./bin;tptp-automat ion-client.jar org.eclipse.hyades.automation.client.adapters.shell.AutomationCli entAdapter -configfile cosmos.config Test started! Test 'junits/TestQueryInputTransformer.testsuite' executing Waiting..... Collected results: 'org.eclipse.hyades.models.common.testprofile.impl.TPFExecuti onResultImpl@63666366 (eProxyURI: platform:/resource/org.eclipse.cosmos.dc.cmdbf .services.tests/TestQueryInputTransformer_1207648353156.execution#C4E6EF1CFD1ADD 600AA0EA40781011DC)' Test 'junits/TestQueryInputTransformer.testsuite' completed Test completed! I verified the same with TPTP 4.4.1 as well as TPTP 4.5 and in either case it fails while trying to execute the testcase with the internal RAC. Hence I conclude that this is a problem with the internal RAC or the way it is launched. Work around is to start RAC externally before executing the test case.
Transferring to the IAC Component Lead since the test executes using the Agent Controller on both 4.4.1/4.5. That is, there are no classpath issues with the test suites. Bobby: Please attach the \eclipse\plugins\org.eclipse.tptp.platform.ac.linux_ia32_4.4.1.v200802050100\agent_controller\config\servicelog.log file to the defect.
This defect is required for the ToG effort. Joanna: Samson is still the default owner of this component.
Created attachment 95709 [details] tptp441_servicelog.log As discussed with Paul, here comes the servicelog.log from \tptp.runtime.allInOne.win32.win32.x86-TPTP-4.4.1\eclipse\plugins\org.eclipse.tptp.platform.ac.win_ia32_4.4.1.v200802050100\agent_controller\config It was hanging and I had to break the process. E:\Bobz\workarea\tptp.runtime.allInOne.win32.win32.x86-TPTP-4.4.1\eclipse\plugins\org.eclipse.hyades .execution_4.4.100.v200802221314>java -cp ./bin;tptp-automation-client.jar org.eclipse.hyades.automa tion.client.adapters.shell.AutomationClientAdapter -configfile cosmos.config Test started! Test 'junits/TestQueryInputTransformer.testsuite' executing org.eclipse.hyades.internal.execution.local.control.InactiveProcessException at org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub.launch(TestExecutio nHarnessExecutorStub.java:422) at org.eclipse.hyades.execution.harness.TestExecutionHarness.launchTestExecution(TestExecuti onHarness.java:2098) at org.eclipse.hyades.execution.harness.TestExecutionHarness.access$2(TestExecutionHarness.j ava:1830) at org.eclipse.hyades.execution.harness.TestExecutionHarness$2.run(TestExecutionHarness.java :750) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) java.lang.RuntimeException: org.eclipse.hyades.internal.execution.local.control.InactiveProcessExcep tion at org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub.handleException(Tes tExecutionHarnessExecutorStub.java:347) at org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub.launch(TestExecutio nHarnessExecutorStub.java:434) at org.eclipse.hyades.execution.harness.TestExecutionHarness.launchTestExecution(TestExecuti onHarness.java:2098) at org.eclipse.hyades.execution.harness.TestExecutionHarness.access$2(TestExecutionHarness.j ava:1830) at org.eclipse.hyades.execution.harness.TestExecutionHarness$2.run(TestExecutionHarness.java :750) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: org.eclipse.hyades.internal.execution.local.control.InactiveProcessException at org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub.launch(TestExecutio nHarnessExecutorStub.java:422) ... 4 more org.eclipse.core.runtime.CoreException: IWAT4039E The Test Execution Harness reported the following problems:org.eclipse.hyades.internal.execution.local.control.InactiveProcessException at org.eclipse.hyades.test.core.launch.delegates.AbstractLaunchConfigurationDelegate2.launch (AbstractLaunchConfigurationDelegate2.java:195) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:759) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:608) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:601) at org.eclipse.hyades.test.core.services.AbstractTestExecutionService.launch(AbstractTestExe cutionService.java:795) at org.eclipse.hyades.test.core.services.AbstractTestExecutionService.execute(AbstractTestEx ecutionService.java:583) at org.eclipse.hyades.automation.server.AbstractService.execute(AbstractService.java:43) at org.eclipse.hyades.automation.server.ServiceProxy$1.run(ServiceProxy.java:141) at org.eclipse.hyades.automation.core.utils.ReusableThread.run(ReusableThread.java:131) at java.lang.Thread.run(Thread.java:810) Terminate batch job (Y/N)? y
Boddy, how long is your Eclipse path? Can you try to move the eclipse directory like D:\eclipse and try it again?
Created attachment 95935 [details] windows crash report - tptp 1) tptp.runtime.allInOne.win32.win32.x86-TPTP-4.5.0M5.zip Reduced path to E:\tptpM5\eclipse, Says completed, but dll crashes (reports windows), test results created though. E:\tptpM5\eclipse\plugins\org.eclipse.hyades.execution_4.4.100.v200801150400>java -cp ./bin;tptp-automation-client.jar org.eclipse.hyades.automation.client.adapters.shell.AutomationClientAdapter -conf igfile cosmos.config Test started! Test 'junits/TestQueryInputTransformer.testsuite' executing Waiting.... Collected results: 'org.eclipse.hyades.models.common.testprofile.impl.TPFExecutionResultImpl@52f452f 4 (eProxyURI: platform:/resource/org.eclipse.cosmos.dc.cmdbf.services.tests/TestQueryInputTransformer.execution#C4E6EF1CFD1ADD600AA0EA40781011DC)' Test 'junits/TestQueryInputTransformer.testsuite' completed Test completed! Windows pop up - ACServer.exe has encountered a problem and needs to close. We are sorry for the incovenience <Send Error Report> <Dont Send> 2) tptp.runtime.allInOne.win32.win32.x86-TPTP-4.4.1.zip Reduced path to E:\tptp441\eclipse, again InactiveProcessException, no test results. Send me a note if you want to access my machine for further diagnosis.
(In reply to comment #12) > Reduced path to E:\tptpM5\eclipse, Says completed, but dll crashes (reports > windows), test results created though. I tried with M5, it worked for me when I installed Eclipse under D:\eclipse and D:\TPTP\Testing\4.5\m5\eclipse. Result file was generated but I didn't get the dll warning. Boddy, I can't read the dll attachment. Is it a screen shot? What does the message say? > E:\tptpM5\eclipse\plugins\org.eclipse.hyades.execution_4.4.100.v200801150400>java > -cp ./bin;tptp-automation-client.jar > org.eclipse.hyades.automation.client.adapters.shell.AutomationClientAdapter > -conf When I tried to run it, I got error: D:\TPTP\Testing\4.5\m5\eclipse\plugins\org.eclipse.hyades.execution_4.4.100.v200 801150400>java -cp ./bin;tptp-automation-client.jar org.eclipse.hyades.automatio n.client.adapters.shell.AutomationClientAdapter -configfile cosmos.config Exception in thread "main" java.lang.NoClassDefFoundError: com/ibm/icu/text/Mess ageFormat at org.eclipse.hyades.automation.client.adapters.shell.CommandLineArgume ntParser.parseConfigFile(CommandLineArgumentParser.java:268) at org.eclipse.hyades.automation.client.adapters.shell.AutomationClientA dapter.main(AutomationClientAdapter.java:200) Do I need to add some env variable to run this? > 2) tptp.runtime.allInOne.win32.win32.x86-TPTP-4.4.1.zip > Reduced path to E:\tptp441\eclipse, again InactiveProcessException, no test I have compiler error using cosmos-sdk-incubation-COSMOS-1.0.0-200802261616.zip. Which version of cosmos should I use with 4.4.1? Boddy, this could be related to 221701 where Java process crashes because its argument exceeds max length. But I need to try with TPTP 4.4.1 before drawing any conclusion.
Did you install the cosmos sdk into eclipse? http://www.eclipse.org/cosmos/downloads/?ver=1.0.0 Make sure the test project compiles fine in your eclipse workbench and use the same workspace for command line execution using TPTP automation client. The dll attachment is an XML file, the technical error report generated by windows on crash. You can open it if you save to disk instead of opening directly in browser. org.eclipse.cosmos.dc.cmdbf.services.tests plug-in has a dependency on org.eclipse.cosmos.common.tests. Please checkout the same from org.eclipse.cosmos/tests/common in same repository Also make sure you have java 5.
Created attachment 96124 [details] Screenshot: Can't view the dll error report
Created attachment 96125 [details] JUnit Test Result with TPTP 441
Bobby, I still can't view the dll error and the page doesn't give me the 'Download the attachment instead' option. I just tried with the TPTP 4.4.1 all-in-one file installation and was able to run the JUnit test with no problem. I've attached the Eclipse screenshot. I tried with 4.5 M5 yesterday and it worked too on my machine. I still have the following error: > E:\tptpM5\eclipse\plugins\org.eclipse.hyades.execution_4.4.100.v200801150400>java > -cp ./bin;tptp-automation-client.jar > org.eclipse.hyades.automation.client.adapters.shell.AutomationClientAdapter > -conf When I tried to run it, I got error: D:\TPTP\Testing\4.5\m5\eclipse\plugins\org.eclipse.hyades.execution_4.4.100.v200 801150400>java -cp ./bin;tptp-automation-client.jar org.eclipse.hyades.automatio n.client.adapters.shell.AutomationClientAdapter -configfile cosmos.config Exception in thread "main" java.lang.NoClassDefFoundError: com/ibm/icu/text/Mess ageFormat at org.eclipse.hyades.automation.client.adapters.shell.CommandLineArgume ntParser.parseConfigFile(CommandLineArgumentParser.java:268) at org.eclipse.hyades.automation.client.adapters.shell.AutomationClientA dapter.main(AutomationClientAdapter.java:200) Do I need to add some env variable to run this? Again, I think this could be related to 221701 where Java process crashes because its argument exceeds max length. Jonathan is working on the fix, targeting this week. Can you try 4.4.1 on some other machines installing Eclipse under D:\?
The error in comment #17 is a regression. We do not regularly test the shell adapter in our test passes. What happened was that when the change was made throughout our code to use the IBM package to format strings, we added the following: import com.ibm.icu.text.MessageFormat; Since the client side of the shell adapter is not running eclipse, this package is not available. If your config file and command line are correct, this would not happen. The error was that the specified config file was not found. So, the cosmos.config was not in the current directory where the shell adapter was kicked off. Obviously, the com.ibm.icu.text.MessageFormat problem needs to be fixed as well.
(In reply to comment #18) > The error was that the specified config file was not found. So, > the cosmos.config was not in the current directory where the shell adapter was > kicked off. Duwayne, thanks for the clarification. Any idea where can i get the cosmos.config? I searched the cosmos plugins and couldn't find it there.
Created attachment 96232 [details] 7825_appcompat.txt I am attaching the "95935: windows crash report - tptp" again.
Created attachment 96233 [details] cosmos.config I am attaching cosmos.config file. This contains the params for the automation shell client like eclipse, workspace locations etc. Please modify according to your environment before using. Also regarding the InactiveProcessException exception, make sure that no RAC is running in your system and your test execution creates a new process while running (internally).
If you can't view any of the attachments in the browser, suggest to right click the link, for example 7825_appcompat.txt above, and select the option to save/download the link. (IE - Save Target As, Firefox - Save Link As)
Created attachment 96276 [details] Screenshot of runing testsuite from command line Bobby, I tried to run the testsuite using the cosmos.config from command line. Both 4.4.1 and 4.5 M5 worked. In each case test was completed and IAC was started. I've attached the screenshot.
(In reply to comment #23) > Created an attachment (id=96276) [details] > Screenshot of runing testsuite from command line > > Bobby, I tried to run the testsuite using the cosmos.config from command line. > Both 4.4.1 and 4.5 M5 worked. In each case test was completed and IAC was > started. > > I've attached the screenshot. > Bobby, were are the TPTP plug-ins installed under Eclipse (e.g. <Eclipse installation directory>/eclipse/plugins or <Eclipse installation directory>/eclipse/dropins)?
/eclipse/plugins, no dropins folder, eclipse ver is Version: 3.4.0 Build id: I20080207-1530 Bing, can you please let me know your Java ver details? I believe Paul could also reproduce the issue.. and the same has happened to me on multiple machines...
(In reply to comment #18) > The error in comment #17 is a regression. We do not regularly test the shell > adapter in our test passes. See defect #228804 for new tests to cover the verify/execute/interrogate/publish test services for Ant, shell, Java clients: /org.eclipse.hyades.test.core.services.tests/manual/Test.Execution.Services.testsuite > What happened was that when the change was made > throughout our code to use the IBM package to format strings, we added the > following: > > import com.ibm.icu.text.MessageFormat; > > Since the client side of the shell adapter is not running eclipse, this package > is not available. If your config file and command line are correct, this would > not happen. The error was that the specified config file was not found. So, > the cosmos.config was not in the current directory where the shell adapter was > kicked off. > > Obviously, the com.ibm.icu.text.MessageFormat problem needs to be fixed as > well. > See defect #228873.
Tried with tptp.runtime.allInOne.win32.win32.x86-TPTP-4.5.0M6.zip and following Java SDKs, still works only with external RAC started, when invoked from command line thru ANT. Test case executes fine in Eclipse workbench. IBM - JDK 5 java version "1.5.0" Java(TM) 2 Runtime Environment, Standard Edition (build pwi32dev-20080315 (SR7)) IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-20080315 (JIT enabled) J9VM - 20080314_17962_lHdSMr JIT - 20080130_0718ifx2_r8 GC - 200802_08) JCL - 20080314 SUN - JDK 5 java version "1.5.0_12" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode, sharing) Eclipse path is short - E:\tptp45M6\eclipse E:\tptp45M6\workspace
Sorry, the ant xml was still pointing to the old M5 driver. Updated and retested, but got the following error: test-execution: [echo] Executing test suite... [tptp:execution] Adding file "E:\tptp45M6\workspace\org.eclipse.cosmos.dc.cmdbf.services.tests\junits\AllTests.testsuite". [tptp:execution] Test execution started. [tptp:execution] Test 'junits\AllTests.testsuite' started. [tptp:execution] Preparing launch delegate... [tptp:execution] Performing pre-launch check... [tptp:execution] Performing final launch validation... [tptp:execution] Initializing source locator... [tptp:execution] Launching delegate... [tptp:execution] org.eclipse.core.runtime.CoreException: IWAT4039E The Test Execution Harness reported the following problems:IWAT0016E The Agent Controller is not available on host localhost. [tptp:execution] Make sure that: [tptp:execution] * the Agent Controller is installed. [tptp:execution] * the Agent Controller is configured to communicate with your machine. [tptp:execution] * you have the correct host name and port number for the Agent Controller. [tptp:execution] at org.eclipse.hyades.test.core.launch.delegates.AbstractLaunchConfiguration Delegate2.launch(AbstractLaunchConfigurationDelegate2.java:221) [tptp:execution] at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigur ation.java:764) [tptp:execution] at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigur ation.java:614) [tptp:execution] at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigur ation.java:607) [tptp:execution] at org.eclipse.hyades.test.core.services.AbstractTestExecutionService.launch (AbstractTestExecutionService.java:816) [tptp:execution] at org.eclipse.hyades.test.core.services.AbstractTestExecutionService.execut e(AbstractTestExecutionService.java:586) [tptp:execution] at org.eclipse.hyades.automation.server.AbstractService.execute(AbstractServ ice.java:43) [tptp:execution] at org.eclipse.hyades.automation.server.ServiceProxy$1.run(ServiceProxy.java :139) [tptp:execution] at org.eclipse.hyades.automation.core.utils.ReusableThread.run(ReusableThrea d.java:131) [tptp:execution] at java.lang.Thread.run(Unknown Source) BUILD FAILED
Bobby, can you attach your IAC config xml file?
Created attachment 98422 [details] serviceconfig.xml I am attaching the serviceconfig.xml from E:\tptp45M6\eclipse\dropins\eclipse\plugins\org.eclipse.tptp.platform.ac.win_ia32_4.4.1.v200803041120\agent_controller\config. Hope this is what you meant by IAC config file..
Created attachment 98423 [details] servicelog.log Also attaching the IAC log....
Bobby, 224134 has been fixed. Can you try your test case again using this build: http://www.eclipse.org/tptp/home/downloads/?buildId=TPTP-4.5.0-200804240100.
Using the new driver, I get the following error when trying to run automation-client-adapter.bat -configfile cosmos.config Content of cosmos.config eclipse = E:\Bobz\TPTP-4.5.0-200804240100\eclipse workspace = E:\Bobz\TPTP-4.5.0-200804240100\workspace project = org.eclipse.cosmos.dc.cmdbf.services.tests suite = junits/TestQueryInputTransformer.testsuite E:\Bobz\TPTP-4.5.0-200804240100\eclipse\dropins\eclipse\plugins\org.eclipse.hyades.execution_4.4.200 .v200804161128>java -cp ./bin;tptp-automation-client.jar org.eclipse.hyades.automation.client.adapte rs.shell.AutomationClientAdapter -configfile cosmos.config java.lang.NoClassDefFoundError: org.eclipse.osgi.util.NLS at java.lang.ClassLoader.defineClassImpl(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:258) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:151) at java.net.URLClassLoader.defineClass(URLClassLoader.java:589) at java.net.URLClassLoader.access$400(URLClassLoader.java:123) at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1034) at java.security.AccessController.doPrivileged(AccessController.java:279) at java.net.URLClassLoader.findClass(URLClassLoader.java:491) at java.lang.ClassLoader.loadClass(ClassLoader.java:631) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:328) at java.lang.ClassLoader.loadClass(ClassLoader.java:597) at org.eclipse.hyades.automation.client.strategies.AbstractExecutionStrategy.redirectConsole (AbstractExecutionStrategy.java:154) at org.eclipse.hyades.automation.client.strategies.OutOfProcessStrategy.execute(OutOfProcess Strategy.java:289) at org.eclipse.hyades.automation.client.ServiceProxy.execute(ServiceProxy.java:77) at org.eclipse.hyades.automation.client.AutomationClient$Default.execute(AutomationClient.ja va:160) at org.eclipse.hyades.automation.client.adapters.java.AutomationClientAdapter.execute(Automa tionClientAdapter.java:176) at org.eclipse.hyades.automation.client.adapters.java.AutomationClientAdapter.execute(Automa tionClientAdapter.java:154) at org.eclipse.hyades.automation.client.adapters.shell.AutomationClientAdapter.main(Automati onClientAdapter.java:227) Works fine from Eclipse workbench (Run As -> Test) Am I missing something? Or the dropins folder in new eclipse created some classpath issue?
(In reply to comment #33) Please see https://bugs.eclipse.org/bugs/show_bug.cgi?id=228873.
The ant execution also failed with same result as M6 - The Agent Controller is not available on host localhost. E:\Bobz\workarea\COSMOS\TestAuto>ant -lib E:\Bobz\workarea\COSMOS\TestAuto\45m6_ant -f TPTP-4.5.0-200804240100_publish.xml -Dtptp.driver=E:\Bobz\TPTP-4.5.0-200804240100\eclipse -Dworkspace=E:\Bobz\TPTP-4.5.0-200804240100\workspace -DoutFolder=E:\Bobz\workarea\COSMOS\TestAuto\Test_Results\report.html -Dworkspace.project=org.eclipse.cosmos.dc.cmdbf.services.tests -Dtestsuite.list=org.eclipse.cosmos.tests\*.testsuite -Dstarttime="11/22/2007 11:45 AM" Buildfile: TPTP-4.5.0-200804240100_publish.xml test-execution: [echo] Executing test suite... [tptp:execution] Adding file "E:\Bobz\TPTP-4.5.0-200804240100\workspace\org.eclipse.cosmos.dc.cmdbf.services.tests\junits\AllTests.testsuite". [tptp:execution] Test execution started. [tptp:execution] Test 'junits\AllTests.testsuite' started. [tptp:execution] Preparing launch delegate... [tptp:execution] Performing pre-launch check... [tptp:execution] Performing final launch validation... [tptp:execution] Initializing source locator... [tptp:execution] Launching delegate... [tptp:execution] org.eclipse.core.runtime.CoreException: IWAT4039E The Test Execution Harness reported the following problems: IWAT0016E The Agent Controller is not available on host localhost. [tptp:execution] Make sure that: [tptp:execution] * the Agent Controller is installed. [tptp:execution] * the Agent Controller is configured to communicate with your machine. [tptp:execution] * you have the correct host name and port number for the Agent Controller. [tptp:execution] at org.eclipse.hyades.test.core.launch.delegates.AbstractLaunchConfiguration Delegate2.launch(AbstractLaunchConfigurationDelegate2.java:225) [tptp:execution] at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigur ation.java:764) [tptp:execution] at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigur ation.java:614) [tptp:execution] at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigur ation.java:607) [tptp:execution] at org.eclipse.hyades.test.core.services.AbstractTestExecutionService.launch (AbstractTestExecutionService.java:816) [tptp:execution] at org.eclipse.hyades.test.core.services.AbstractTestExecutionService.execut e(AbstractTestExecutionService.java:586) [tptp:execution] at org.eclipse.hyades.automation.server.AbstractService.execute(AbstractServ ice.java:43) [tptp:execution] at org.eclipse.hyades.automation.server.ServiceProxy$1.run(ServiceProxy.java :139) [tptp:execution] at org.eclipse.hyades.automation.core.utils.ReusableThread.run(ReusableThrea d.java:131) [tptp:execution] at java.lang.Thread.run(Unknown Source) BUILD FAILED E:\Bobz\workarea\COSMOS\TestAuto\TPTP-4.5.0-200804240100_publish.xml:27: java.lang.NullPointerException Total time: 2 minutes 1 second Found this in the eclpse .log file !SESSION 2008-05-05 17:33:40.187 ----------------------------------------------- eclipse.buildId=I20080415-1646 java.version=1.5.0_12 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Framework arguments: -application org.eclipse.hyades.execution.server Command-line arguments: -os win32 -ws win32 -arch x86 -application org.eclipse.hyades.execution.server -data E:\Bobz\TPTP-4.5.0-200804240100\workspace !ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2008-05-05 17:33:51.718 !MESSAGE Execution framework config file is invalid. This could be caused by the execution plugin checked out in your workspace. !ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2008-05-05 17:33:51.765 !MESSAGE Execution framework config file is invalid. This could be caused by the execution plugin checked out in your workspace. !ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2008-05-05 17:33:51.765 !MESSAGE IAC could not be started due to invalid configuration files. !ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2008-05-05 17:34:41.312 !MESSAGE Execution framework config file is invalid. This could be caused by the execution plugin checked out in your workspace. !ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2008-05-05 17:34:41.343 !MESSAGE Execution framework config file is invalid. This could be caused by the execution plugin checked out in your workspace. !ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2008-05-05 17:34:41.359 !MESSAGE IAC could not be started due to invalid configuration files.
Thanks Paul, updated automation-client-adapter.bat to include the jars, and now failed with the error - IWAT0016E The Agent Controller is not available on host localhost. (same as ant execution)
Bobby, can you attach your new serviceconfig.xml and a list of projects in your workspace?
Created attachment 98702 [details] TPTP-4.5.0-200804240100-serviceconfig.xml serviceconfig file is attached. I have only two projects in my workspace, 1) org.eclipse.cosmos.common.tests 2) org.eclipse.cosmos.dc.cmdbf.services.tests Please refer initial comments on the bug report for more info on these projects.
Bobby, can you modify the following line in your your service config xml file: <Variable name="CLASSPATH_ORG_ECLIPSE_SWT" position="append" value="E:\Bobz\TPTP-4.5.0-200804240100\eclipse\plugins\org.eclipse.swt_3.4.0.v3439.jar" /> You need to append the other SWT jars to the end. My config file looks like: <Variable name="CLASSPATH_ORG_ECLIPSE_SWT" position="append" value="D:\TPTP\Development\4.5\eclipse\plugins\org.eclipse.swt.win32.win32.x86.source_3.4.0.v3439.jar;D:\TPTP\Development\4.5\eclipse\plugins\org.eclipse.swt.win32.win32.x86_3.4.0.v3439.jar;D:\TPTP\Development\4.5\eclipse\plugins\org.eclipse.swt_3.4.0.v3439.jar"/> This was reported in bug 228856 and has been fixed in builds after May 1, 2008. Not sure if your problem is caused by this but let's get that out of the way first.
Bing, I tried to modify the serviceconfig.xml as you suggested, but it seems when I run the test it is reverted back to original values. (so I guess in effect the change is not taken) Also looking at the windows processes (Task Manager) while executing the test, ACServer.exe doesn't seem to get started at all.
Can you try TPTP-4.5.0-200805011405 build (http://www.eclipse.org/tptp/home/downloads/?buildId=TPTP-4.5.0-200805011405)? If ACServer does not start, then please attach the config and log. Thanks.
Created attachment 99032 [details] TPTP-4.5.0-200805011405-logs.zip Tried new build (TPTP-4.5.0-200805011405), but still the same error - IWAT0016E The Agent Controller is not available on host localhost. Attaching the IAC logs and config.
Bobby, did you download the all-in-one package or separate files? The latest TPTP includes P2 which changes where you installed Eclipse plugins. The quickest way is to use the all-in-one package and TPTP is installed under <Eclipse>/dropins/eclipse/plugins.
Hi Bing, I installed the tptp.runtime.allInOne.win32.win32.x86-TPTP-4.5.0-200805011405.zip.
Bobby, can you check the org.eclipse.hyades.execution_<version> under E:\Bobz\workarea\TPTP-4.5.0-200805011405\eclipse\dropins\eclipse\plugins to see if there is a non-empty config.jar file.
config.jar in E:\Bobz\workarea\TPTP-4.5.0-200805011405\eclipse\dropins\eclipse\plugins\org.eclipse.hyades.execution_4.4.200.v200804290100 is around 5.39 KB
Bing, this is required by Test for i8. Please work on a resolution
I couldn't reproduce this. Will try with M8 build. Meanwhile, will ask Tony to try on his machine.
I tried to reporduce it with following steps: 1. Install TPTP-4.5.0-200805011405 (http://www.eclipse.org/tptp/home/downloads/?buildId=TPTP-4.5.0-200805011405) using the All-In-One zip file. 2. Install TPTP-4.5.0-200805011405 stand-alone AC. 3. Install the cosmos zip in <Eclipse>/dropins cosmos-sdk-incubation-COSMOS-1.0.0-200802261616.zip 4. In your new workbench, checkout org.eclipse.cosmos/tests/data-collection/org.eclipse.cosmos.dc.cmdbf.services.tests and org.eclipse.cosmos/tests/common from dev.eclipse.org, /cvsroot/technology 5. Config and start standalone AC 6. Right click any testsuite (eg: TestQueryInputTransformer.testsuite) and Runs as -> Test Both AC and IAC are working, i can generate some executions by running junit tests in those imported projects But the only problem is the test may not run properly for the first time(InactiveProcessException sometimes, occured in AC in my testing), but we still can get the executions from the second launch.
Bobby, can you try this TPTP build: http://www.eclipse.org/tptp/home/downloads/?buildId=TPTP-4.5.0-200805190100? It contains the fix for 229189.
Tried tptp.runtime.allInOne.win32.win32.x86-TPTP-4.5.0-200805190100.zip From the automation framework (using ant), I got the following error: [tptp:execution] Test execution started. [tptp:execution] Test 'org.eclipse.cosmos.dc.cmdbf.services.tests\junits\TestCMDBfDeregistrationOper ation.testsuite' started. [tptp:execution] Preparing launch delegate... [tptp:execution] Performing pre-launch check... [tptp:execution] Performing final launch validation... [tptp:execution] Initializing source locator... [tptp:execution] Launching delegate... [tptp:execution] org.eclipse.core.runtime.CoreException: IWAT4039E The Test Execution Harness reported the following problems: IWAT0016E The Agent Controller is not available on host localhost. To confirm I ran the platform-verification too platform-verification: [echo] Verifying connection... [condition] Verification started! [condition] Verifying connection: [condition] {connectionString=tptp:rac://localhost:10002/default, specification=tptp, serverClass=rac, host=localhost, port=10002, serverInstance=/default, user=null, password=null} [condition] The specified agent controller 'tptp:rac://localhost:10002/default' The specified agent controller cannot be contacted! [condition] Verification completed! But it works fine when RAC started externally From workbench, it worked fine. I used the same eclipse from automation, so not sure about the first time failure mentioned by Tony. But even after working fine from workbench, same setup fails from automation client. Does it mean it is only partly fixed?
Kendric and I tried the 0519 build and got some errors. Then we tried 0523 and was able to profile external java app and run a JUnit test. Bobby, can you try this build http://www.eclipse.org/tptp/home/downloads/?buildId=TPTP-4.5.0-200805230100. A lot of fixes has gone into 0520's build according to http://www.eclipse.org/tptp/home/downloads/4.5.0/drops/cvsActivity/TPTP-4.5.0-200805201942.html.
Tested using the following: birt-report-framework-2_3_0-N20080515.zip cosmos-rm-incubation-sdk-COSMOS-1.0.0-200805261443.zip cosmos-sdk-incubation-COSMOS-1.0.0-200805261443.zip dtp-1.6RC1.zip GEF-runtime-I200805121830.zip org.eclipse.tptp.test.report.birt-TPTP-4.5.0-200805230100.zip tptp.runtime.allInOne.win32.win32.x86-TPTP-4.5.0-200805230100.zip Failed with following error: [tptp:execution] Test execution started. [tptp:execution] Test 'org.eclipse.cosmos.dc.cmdbf.services.tests\junits\TestCMDBfDeregistrationOper ation.testsuite' started. [tptp:execution] Preparing launch delegate... [tptp:execution] Performing pre-launch check... [tptp:execution] Performing final launch validation... [tptp:execution] Initializing source locator... [tptp:execution] Launching delegate... [tptp:execution] org.eclipse.core.runtime.CoreException: IWAT4039E The Test Execution Harness report ed the following problems: IWAT0016E The Agent Controller is not available on host localhost. [tptp:execution] Make sure that: [tptp:execution] * the Agent Controller is installed. [tptp:execution] * the Agent Controller is configured to communicate with your machine. [tptp:execution] * you have the correct host name and port number for the Agent Controller. [tptp:execution] at org.eclipse.hyades.test.core.launch.delegates.AbstractLaunchConfiguration Delegate2.launch(AbstractLaunchConfigurationDelegate2.java:225)
Created attachment 102076 [details] 45_publish.xml You can reproduce the error using the attached build script. Run using the following command: ant.bat -lib 45m6_ant -f 45_publish.xml -Dbuild_space=<GIVE ANY FOLDER NAME WITH ABSOLUTE PATH> eg: ant.bat -lib 45m6_ant -f 45_publish.xml -Dbuild_space=E:/Bobz/workarea/COSMOS/TestAuto/45_tmp Folder 45m6_ant should contain: ant-tptp.jar com.ibm.icu_3.8.1.v20080402.jar org.eclipse.osgi_3.4.0.v20080427-0830.jar TestAuto.jar (will attach) folder 45_test_setup should contain: birt-report-framework-2_3_0-N20080515.zip dtp-1.6RC1.zip GEF-runtime-I200805121830.zip org.eclipse.tptp.test.report.birt-TPTP-4.5.0-200805230100.zip tptp.runtime.allInOne.win32.win32.x86-TPTP-4.5.0-200805230100.zip The latest cosmos drivers for testing will be automatically downloaded. It works fine when external RAC is started. But now report generation fails with following error: [tptp:publication] java.lang.NullPointerException [tptp:publication] at java.lang.String.concat(Unknown Source) [tptp:publication] at org.eclipse.tptp.platform.report.birt.core.internal.impl.HtmlSortWrapper. getHeader(HtmlSortWrapper.java:176) [tptp:publication] at org.eclipse.tptp.platform.report.birt.core.provisional.BIRTReportGenerato r.generateHTMLReport(BIRTReportGenerator.java:201) [tptp:publication] at org.eclipse.tptp.test.report.birt.internal.elements.TabularTPFTestSuiteRe portElement.generate(TabularTPFTestSuiteReportElement.java:228) [tptp:publication] at org.eclipse.tptp.test.report.birt.services.TestSuitesTabularPublicationSe rvice.publish(TestSuitesTabularPublicationService.java:86) [tptp:publication] at org.eclipse.hyades.test.core.services.AbstractTestResultsPublicationServi ce.execute(AbstractTestResultsPublicationService.java:105)
Created attachment 102077 [details] TestAuto.jar Copy this to the 45m6_ant folder
Bobby, I installed the TPTP all-in-one and cosmos zip and run the TestQueryInputTransformer.testsuite file. I was able to run it successfully 3 times. I got this error when running TestCMDBfDeregistrationOperation.testsuite: java.io.FileNotFoundException: c:\temp\tmp\cosmos.rm.cmdbf\testItemRequest.txt (The system cannot find the path specified) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.<init>(Unknown Source) at java.io.FileOutputStream.<init>(Unknown Source) ..... Because the error you got says that IAC is not avaiable, can you try to profile a external Java class using IAC? It would help us to determine if the problem is with IAC or Test framework. How many times have you tried to run the JUnit testsuite? If haven't done so, can you try to run it 3-5 times
Same result with Release Candidate Build: TPTP-4.5.0RC2-200805271330 too. Any idea why the null pointer exception while report generation? Bing, the test execution works fine from the workbench (without external RAC). But from automation framework I get the error: [tptp:execution] org.eclipse.core.runtime.CoreException: IWAT4039E The Test Execution Harness report ed the following problems: IWAT0016E The Agent Controller is not available on host localhost. [tptp:execution] Make sure that: [tptp:execution] * the Agent Controller is installed. [tptp:execution] * the Agent Controller is configured to communicate with your machine. [tptp:execution] * you have the correct host name and port number for the Agent Controller. [tptp:execution] at org.eclipse.hyades.test.core.launch.delegates.AbstractLaunchConfiguration Delegate2.launch(AbstractLaunchConfigurationDelegate2.java:225) [tptp:execution] at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigur ation.java:764) [tptp:execution] at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigur ation.java:614) [tptp:execution] at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigur ation.java:607) [tptp:execution] at org.eclipse.hyades.test.core.services.AbstractTestExecutionService.launch (AbstractTestExecutionService.java:822) [tptp:execution] at org.eclipse.hyades.test.core.services.AbstractTestExecutionService.execut e(AbstractTestExecutionService.java:592) [tptp:execution] at org.eclipse.hyades.automation.server.AbstractService.execute(AbstractServ ice.java:43) [tptp:execution] at org.eclipse.hyades.automation.server.ServiceProxy$1.run(ServiceProxy.java :139) [tptp:execution] at org.eclipse.hyades.automation.core.utils.ReusableThread.run(ReusableThrea d.java:131) [tptp:execution] at java.lang.Thread.run(Unknown Source) I am automating right from eclipse installation, so it has to work at the first time itself.
Increase severity since there is no work-around.
(In reply to comment #57) > Any idea why the null pointer exception while report generation? See defect #234771. > Bing, the test execution works fine from the workbench (without external RAC). > But from automation framework I get the error: > > [tptp:execution] org.eclipse.core.runtime.CoreException: IWAT4039E The Test > Execution Harness report > ed the following problems: IWAT0016E The Agent Controller is not available on > host localhost. > [tptp:execution] Make sure that: > [tptp:execution] * the Agent Controller is installed. > [tptp:execution] * the Agent Controller is configured to communicate with your > machine. > [tptp:execution] * you have the correct host name and port number for the Agent > Controller. > [tptp:execution] at > org.eclipse.hyades.test.core.launch.delegates.AbstractLaunchConfiguration > Delegate2.launch(AbstractLaunchConfigurationDelegate2.java:225) > [tptp:execution] at > org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigur > ation.java:764) > [tptp:execution] at > org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigur > ation.java:614) > [tptp:execution] at > org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigur > ation.java:607) > [tptp:execution] at > org.eclipse.hyades.test.core.services.AbstractTestExecutionService.launch > (AbstractTestExecutionService.java:822) > [tptp:execution] at > org.eclipse.hyades.test.core.services.AbstractTestExecutionService.execut > e(AbstractTestExecutionService.java:592) > [tptp:execution] at > org.eclipse.hyades.automation.server.AbstractService.execute(AbstractServ > ice.java:43) > [tptp:execution] at > org.eclipse.hyades.automation.server.ServiceProxy$1.run(ServiceProxy.java > :139) > [tptp:execution] at > org.eclipse.hyades.automation.core.utils.ReusableThread.run(ReusableThrea > d.java:131) > [tptp:execution] at java.lang.Thread.run(Unknown Source) > > > I am automating right from eclipse installation, so it has to work at the first > time itself. Note, launching a test from ASF requires the Agent Controller to be installed on the target machine (SUT).
Dywayne, seems ASF couldn't connect to IAC. Can you take a look? Only need to look at comments after #53. Thanks.
Sure, the action item is to install RC2 and run a test through ASF without first running the IDE using the IAC, is that correct?
(In reply to comment #61) > Sure, the action item is to install RC2 and run a test through ASF without > first running the IDE using the IAC, is that correct? Correct. And if it fails, which is what Bobby got, can you try with stand-alone AC? Thanks.
Test Results from Friday per comment #61: The IAC did not start either before or after running the IDE once. The serviceconfig.xml file was generated and from a casual glance looked reasonable. Same test running against the stand-alone AC worked fine.
(In reply to comment #63) > Test Results from Friday per comment #61: The IAC did not start either before > or after running the IDE once. The serviceconfig.xml file was generated and > from a casual glance looked reasonable. > Same test running against the stand-alone AC worked fine. Duwayne, can you attach you serviceconfig.xml here. And which JVM your Eclipse uses?
Created attachment 103134 [details] serviceconfig.xml Hi Bing, This was using IBM 1.6 JRE as you can see in the serviceconfig.xml file.
Duwayne, the CLASSPATH_ORG_ECLIPSE_TPTP_PLATFORM_MODELS and CLASSPATH_ORG_ECLIPSE_TPTP_PLATFORM_MODELS_HIERARCHY are null in config file. Can you check if org.eclipse.tptp.platform.models_xxx and org.eclipse.tptp.platform.models.hierarchy_xxx exist in your D:\TPTP\4.5i8_0527\eclipse\dropins\eclipse\plugins directory?
Hi Bing, The error you found in serviceconfig.xml was apparently due to the fact that these plugins were checked-out in the workspace I was using to run the test. So, then I tried today's 0100 build, where the IAC had not been configured or started. Running an Ant task through ASF does not start the IAC nor does the serviceconfig.xml get initialized. The serviceconfig.xml does not get written until the IDE is brought up and a test is run from the IDE. After getting a proper configuration for the IAC, it still will not start from an Ant task through ASF. If I start the IDE and run a task to get the IAC started, the same Ant task runs sucessfully using the instance of the IAC that is running from the IDE. So, the issue is that ASF tasks do not seem to start or configure the IAC.
Currently IAC is invoked in org.eclipse.tptp.platform.execution.client.core.internal.NodeImpl.connect(ConnectionInfo) by calling AutoStartStop.startIAC(). I am not familiar with ASF code. Duwayne, can you check if ASF calls that method or needs to add calls to AutoStartStop.startIAC()?
I can double check, but it looks like we are calling the following: org.eclipse.hyades.internal.execution.local.control.NodeImpl /** * @see Node#connect() */ public synchronized Connection connect(int port) throws AgentControllerUnavailableException, SecureConnectionRequiredException, UntrustedAgentControllerException, LoginFailedException { Connection testConnection = null; /* NM: Bugzilla 173330: Start IAC */ /* First check to see whether the iac.administrator plugin is available */ Bundle iacBundle = Platform.getBundle("org.eclipse.tptp.platform.iac.administrator");//$NON-NLS-1$ if ((iacBundle != null) && (isLocal())) AutoStartStop.startIAC(); /* End of bugzilla 173330 */ I checked an earlier version of TPTP 4.5 that I had laying around and it was working fine. I seem to recall this also worked in M6, but not sure. So, it looks like the real defect is here in local.control.NodeImpl. Hope this is it, that would be an easy fix.
There is something that has regressed in the configuration check when running headless. The errors I am getting are: eclipse.buildId=I20080523-0100 java.fullversion=J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20070817_13537 (JIT enabled) J9VM - 20070817_013537_lHdSMR JIT - dev_20070817_1300 GC - 20070815_AA BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Framework arguments: -application org.eclipse.hyades.execution.server Command-line arguments: -os win32 -ws win32 -arch x86 -application org.eclipse.hyades.execution.server -data D:\tptpi8workspace3 Error Mon Jun 02 16:42:47 EDT 2008 IAC could not be started due to invalid configuration files. Also other error messages: Execution framework config file is invalid. This could be caused by the execution plugin checked out in your workspace. I am getting the same errors with a fresh workspace that has no plugins checked out. Note that the configuration of the IAC is ok since I can run these tests with the IAC from the IDE. This is using today's build. Reference: org.eclipse.tptp.platform.iac.administrator.internal.startstop.AutoStartStop.java If I comment out the following call in StartIAC, the IAC will start and execution will complete. There is then a Dr. Watson at the end, but that may be the result of commenting out the configuration check. The errors do not happen when running the IDE, only when running headless through ASF. /* If configuration is still invalid, return an error */ if (!AdminUtil.isConfigurationValid()) { Status status = new Status(Status.ERROR, AdminPlugin.PLUGIN_ID, "IAC could not be started due to invalid configuration files."); AdminPlugin.getDefault().getLog().log(status); return 1; }
Adding to CC list. As discussed in this morning's AG call, this is a critical defect for a consumming product that uses ASF for command line invocations.
FYI - when running from command line (ant), I do get a pop up in firewall when the first test case is executed... (fresh eclipse, fresh workspace) From firewall log: The user has created a rule to "permit" communications. Outbound TCP connection. Remote address,service is (BOJOSEPH2(192.168.68.1),10002). Process name is "E:\Bobz\workarea\COSMOS\TestAuto\45_tmp\eclipse\eclipse.exe". I don't see ACServer.exe in the process list though (Task Manager)
(In reply to comment #71) > Adding to CC list. As discussed in this morning's AG call, this is a critical > defect for a consumming product that uses ASF for command line invocations. > Duwayne, is the consuming product able to reproduce this behavior? If so, please revert the severity back to critical.
(In reply to comment #70) >> If I comment out the following call in StartIAC, the IAC will start and > execution will complete. Duwayne, were you able to step through the isConfigurationValid() method to see why it failed? I am guessing the following line maybe cause the problem: if (!iacJVM.equals(workbenchJVM)){ AdminPlugin.getDefault().setString(PreferenceMessages.JAVA_EXECUTABLE, workbenchJVM); return false; } You can try to comment them out and see if that fixes ASF. So I guess ASF only invokes Eclipse.exe but not workbench? Am I right?
You are correct, it is the headless eclipse that is the issue. Looks like this is not an issue in the consumming product. Evidently the consumming product has dependencies the "right" plugins so that this works when in headless mode. I didn't find the exact location in the org.eclipse.tptp.platform.iac.administrator, but it is certainly easy to reproduce, just run a TPTP ASF test. Since it is a regression, it should be relatively easy to find the problem.
Added note: I didn't step through with the debugger yet, that requires added steps to kick off eclipse with debug through ASF and attach in the right place to the remote process.
Duwayne, I stepped through the code with Joel's help. The following line fails: AdminUtil.getIACPlugins(){ ... IBundleGroupProvider providers[] = Platform.getBundleGroupProviders(); ... } Seems org.eclipse.core.runtime.Platform.getBundleGroupProviders returns empty list. Could this be caused by race condition? How does ASF launch the headless workbench and the test case?
The tptp-automation-client code in OutOfProcessStrategy.java kicks off headless eclipse via Runtime.getRuntime().exec(commandString) using -application something like this: elipse -nosplash -application... From that point, the tptp-automation-server reads the launch configuration file kicks off the test execution service.
I have not been able to get Paul's plugin to repro the problem yet, I will try over the weekend. I don't think the activator is getting called.
DISREGARD comment 79 above, pasted into wrong defect.
Updated status. During the investigation of comment #77, it was found that: IBundleGroupProvider providers[] = Platform.getBundleGroupProviders(); 1. The above line returns a providers array each time it is called. However, the array is empty (0 length) ONLY when running through ASF. This code actually gets called several times in starting a test execution and the result is the same. 2. The same API works fine when not operating under ASF. 3. This problem is the same in the 4.5 M6 driver and yet does not seem to be affecting a consumming product that launches a different test type through ASF. I do not know why this is the case (that it works there). 4. There is no apparent race condition, the API seems to be returning this empty list even if we wait quite some time before calling. 5. The case of running tests through ASF while using the IAC had not been one of our test pass cases. Thus, it may have been broken for quite some time or indeed may not have ever worked. 6. Platform.isRunning() returns true. According to the API documentation, if isRunning() returns true, getBundleGroupProviders() is supposed to work. I would conclude that the platform API is not working in accordance with the requirements. Other Platform API's, such as getConfigurationLocation() seem to be fine running through ASF. 7. I have not yet found a solution to modify the code using other API's to make this work. If anyone knows a workaround of API's so we don't need to use getBundleGroupProviders(), please speak up.
(In reply to comment #81) > 6. Platform.isRunning() returns true. According to the API documentation, if > isRunning() returns true, getBundleGroupProviders() is supposed to work. I > would conclude that the platform API is not working in accordance with the > requirements. Other Platform API's, such as getConfigurationLocation() seem to > be fine running through ASF. Did you debug org.eclipse.core.internal.runtime.InternalPlatform.getBundleGroupProviders() to determine the root cause of the zero-length return array? For example, does the service tracker return null (e.g. no services being tracked) or zero-lengh array (e.g. no registered services). I would assume that this API is not behaving properly when in a headless environment.
I have traced the issue further into the following class: org.eclipse.osgi.framework.internal.core.ServiceRegistryImpl.java which implements org.eclipse.osgi.framework.adaptor.ServiceRegistry The issue is that when lookupServiceReferences is called to find the org.eclipse.core.runtime.IBundleGroupProvider service, it is not there in the case when running through ASF (it is there when running the IDE). The publishedServicesByClass member of this class has been initialized and contains a HashMap of 33 services, but is missing the IBundleGroupProvider service we are looking for. Thus, the return value it null. I am still working toward finding the reason for this problem. Also, in talking to Joe earlier, this functionality was working in earlier when he was running tests of ASF using the IAC.
Filed a defect against eclipse platform since this really needs to be fixed there. https://bugs.eclipse.org/bugs/show_bug.cgi?id=236709 marked as depends on.
Created attachment 104547 [details] patch for iac.administrator Patch to fix the issue with the IBundleGroupProvider providers[] = Platform.getBundleGroupProviders(); returning an empty list. Paul and Bing, please review.
Patch looks good.
DuWayne, just want to make sure that you have seen the latest append to https://bugs.eclipse.org/bugs/show_bug.cgi?id=236709. Affects the patch I think
(In reply to comment #85) > Created an attachment (id=104547) [details] > patch for iac.administrator > > Patch to fix the issue with the IBundleGroupProvider providers[] = > Platform.getBundleGroupProviders(); returning an empty list. Paul and Bing, > please review. > Reviewed and approved with comments: -Add //$NON-NLS-1$ to Bundle b = Platform.getBundle("org.eclipse.update.configurator");. -Use b.start(Bundle.START_TRANSIENT) as suggested by Thomas (https://bugs.eclipse.org/bugs/show_bug.cgi?id=236709#c7). -Move providers = Platform.getBundleGroupProviders() to under b.start() since it will return an empty list again if b.start(Bundle.START_TRANSIENT) fails.
Created attachment 104550 [details] revised iac.administrator patch Revised patch slightly per further comments from eclipse platform group. Paul and Bing please review final patch.
Patch is good.
PMC approved, delivered patch to iac.administrator to HEAD.
(In reply to comment #89) > Created an attachment (id=104550) [details] > revised iac.administrator patch > > Revised patch slightly per further comments from eclipse platform group. Paul > and Bing please review final patch. > New patch reviewed and approved except the following from my review of the original patch (see comment #88) is still an issue in the new patch: -Add //$NON-NLS-1$ to Bundle b = Platform.getBundle("org.eclipse.update.configurator");. -Move providers = Platform.getBundleGroupProviders() to under b.start() since it will return an empty list again if b.start(Bundle.START_TRANSIENT) fails.
Changing status to fixed.
Verified in 4.5i8.
Closing.
I see that the patch works fine on windows, but fails in Linux with following error: [tptp:execution] org.eclipse.core.runtime.CoreException: IWAT4039E The Test Execution Harness reported the following problems: IWAT0016E The Agent Controller is not available on host localhost. [tptp:execution] Make sure that: [tptp:execution] * the Agent Controller is installed. [tptp:execution] * the Agent Controller is configured to communicate with your machine. [tptp:execution] * you have the correct host name and port number for the Agent Controller. [tptp:execution] at org.eclipse.hyades.test.core.launch.delegates.AbstractLaunchConfigurationDelegate2.launch(AbstractLaunchConfigurationDelegate2.java:225) We do support Linux right? I am attaching the test execution log for your info. Note: Test execution works fine on Linux when external RAC is started.
Created attachment 106213 [details] COSMOS_TestAuto_Linux.log
(In reply to comment #96) > We do support Linux right? Yes.
The test is being launched correctly, but the connection to the IAC cannot be established. Since this scenario worked with the Agent Controller, reassigning to Bing.
(In reply to comment #96) > I see that the patch works fine on windows, but fails in Linux with following > error: > [tptp:execution] org.eclipse.core.runtime.CoreException: IWAT4039E The Test > org.eclipse.hyades.test.core.launch.delegates.AbstractLaunchConfigurationDelegate2.launch(AbstractLaunchConfigurationDelegate2.java:225) > We do support Linux right? I am attaching the test execution log for your info. > Note: Test execution works fine on Linux when external RAC is started. I tried TPTP 4.5 all-in-one on Linux IA32. ASF with headless Eclipse works for me (use Linux properties are here. JVM 1.5 was used. ractest@tptp-blackhawk:~/bing/4.5/eclipse> uname -a Linux tptp-blackhawk 2.6.5-7.97-default #1 Fri Jul 2 14:21:59 UTC 2004 i686 i686 i386 GNU/Linux Bobby, can you describe what failed on your machine?
(In reply to comment #100) > (In reply to comment #96) > > I see that the patch works fine on windows, but fails in Linux with following > > error: > > [tptp:execution] org.eclipse.core.runtime.CoreException: IWAT4039E The Test > > > org.eclipse.hyades.test.core.launch.delegates.AbstractLaunchConfigurationDelegate2.launch(AbstractLaunchConfigurationDelegate2.java:225) > > We do support Linux right? I am attaching the test execution log for your info. > > Note: Test execution works fine on Linux when external RAC is started. > > I tried TPTP 4.5 all-in-one on Linux IA32. ASF with headless Eclipse works for > me (use > > Linux properties are here. JVM 1.5 was used. > > ractest@tptp-blackhawk:~/bing/4.5/eclipse> uname -a > Linux tptp-blackhawk 2.6.5-7.97-default #1 Fri Jul 2 14:21:59 UTC 2004 i686 > i686 i386 GNU/Linux > > Bobby, can you describe what failed on your machine? > Given the following error in the log, could this be somehow related to defect #236464: [Fatal Error] :-1:-1: Premature end of file. The stack trace is different, but the same error is only reported when using the IAC. Bobby, can you try the next 4.5.1 build (http://www.eclipse.org/tptp/home/downloads/?ver=4.5.1)?
Linux ver is : Linux localhost.localdomain 2.6.18-53.el5 #1 SMP Wed Oct 10 16:34:02 EDT 2007 i686 i686 i386 GNU/Linux java version "1.5.0" Java(TM) 2 Runtime Environment, Standard Edition (build pxi32dev-20070201 (SR4)) IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32 j9vmxi3223-20070201 (JIT enabled) J9VM - 20070131_11312_lHdSMR JIT - 20070109_1805ifx1_r8 GC - 200701_09) JCL - 20070126 Output from build TPTP-4.5.1-200807140100 [tptp:execution] Test execution started. [tptp:execution] Test 'org.eclipse.cosmos.dc.cmdbf.services.tests/junits/TestCMDBfDeregistrationOperation.testsuite' started. [tptp:execution] Preparing launch delegate... [tptp:execution] Performing pre-launch check... [tptp:execution] Performing final launch validation... [tptp:execution] Initializing source locator... [tptp:execution] Launching delegate... [tptp:execution] [Fatal Error] :-1:-1: Premature end of file. [tptp:execution] org.eclipse.core.runtime.CoreException: IWAT4039E The Test Execution Harness reported the following problems: IWAT0016E The Agent Controller is not available on host localhost. [tptp:execution] Make sure that: [tptp:execution] * the Agent Controller is installed. [tptp:execution] * the Agent Controller is configured to communicate with your machine. [tptp:execution] * you have the correct host name and port number for the Agent Controller. [tptp:execution] at org.eclipse.hyades.test.core.launch.delegates.AbstractLaunchConfigurationDelegate2.launch(AbstractLaunchConfigurationDelegate2.java:225) [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:822) [tptp:execution] at org.eclipse.hyades.test.core.services.AbstractTestExecutionService.execute(AbstractTestExecutionService.java:592) [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:139) [tptp:execution] at org.eclipse.hyades.automation.core.utils.ReusableThread.run(ReusableThread.java:131) [tptp:execution] at java.lang.Thread.run(Thread.java:803) BUILD FAILED /home/actk/COSMOS/TestAuto/45_publish.xml:459: java.lang.NullPointerException at org.apache.tools.ant.Task.perform(Task.java:373) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) at org.apache.tools.ant.Project.executeTarget(Project.java:1185) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.Main.runBuild(Main.java:668) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67) Caused by: java.lang.NullPointerException at java.util.Hashtable.get(Hashtable.java:482) at org.apache.tools.ant.PropertyHelper.setProperty(PropertyHelper.java:313) at org.apache.tools.ant.Project.setProperty(Project.java:399) at org.eclipse.hyades.automation.client.adapters.ant.AutomationClientAdapter$Execution.execute(AutomationClientAdapter.java:634) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) ... 10 more --- Nested Exception --- java.lang.NullPointerException at java.util.Hashtable.get(Hashtable.java:482) at org.apache.tools.ant.PropertyHelper.setProperty(PropertyHelper.java:313) at org.apache.tools.ant.Project.setProperty(Project.java:399) at org.eclipse.hyades.automation.client.adapters.ant.AutomationClientAdapter$Execution.execute(AutomationClientAdapter.java:634) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) at org.apache.tools.ant.Project.executeTarget(Project.java:1185) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.Main.runBuild(Main.java:668) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67) Total time: 5 minutes 55 seconds
(In reply to comment #102) Note, the NPE is caused by trying to set a non-existent results object due to the failed test execution.
Got the same error even with external RAC running. Used agntctrl.linux_ia32-TPTP-4.4.1 I was hoping it would work with RAC started externally.
(In reply to comment #104) > Got the same error even with external RAC running. > Used agntctrl.linux_ia32-TPTP-4.4.1 > I was hoping it would work with RAC started externally. Bobby, can you try with 4.5 stand-alone AC?
(In reply to comment #105) > (In reply to comment #104) > > Got the same error even with external RAC running. > > Used agntctrl.linux_ia32-TPTP-4.4.1 > > I was hoping it would work with RAC started externally. > > Bobby, can you try with 4.5 stand-alone AC? > See comment #96.
I tried to run TestQueryInputTransformer through ASF on Linux and was able to do it twice. I installed cosmos-sdk-incubation-COSMOS-1.0.0-200802261616.zip and checked out V1_0_0_i9 versions of the two cosmos projects. IAC was started and killed when the headless eclipse exits. And the execution history shows all testcases passed. Bobby, how do I reproduce your error?
It failed with the agent controller from the same build too (4.5.1). Paul, that build (comment #96) worked on linux when RAC started externally. Interestingly, I noticed the same error in windows too, although the execution continues and works fine. So I wonder that error message is kinda harmless and comes only for the very first execution. See "[tptp:execution] [Fatal Error] :-1:-1: Premature end of file" below [tptp:execution] Test execution started. [tptp:execution] Test 'org.eclipse.cosmos.dc.cmdbf.services.tests\junits\TestCMD BfDeregistrationOperation.testsuite' started. [tptp:execution] Preparing launch delegate... [tptp:execution] Performing pre-launch check... [tptp:execution] Performing final launch validation... [tptp:execution] Initializing source locator... [tptp:execution] Launching delegate... [tptp:execution] [Fatal Error] :-1:-1: Premature end of file. [tptp:execution] Waiting..... [tptp:execution] Test result 'TestCMDBfDeregistrationOperation.execution' collec ted. [tptp:execution] Test 'org.eclipse.cosmos.dc.cmdbf.services.tests\junits\TestCMD BfDeregistrationOperation.testsuite' completed. [tptp:execution] Test 'org.eclipse.cosmos.dc.cmdbf.services.tests\junits\TestCMD BfRegistrationOperation.testsuite' started. [tptp:execution] Preparing launch delegate... [tptp:execution] Performing pre-launch check... [tptp:execution] Performing final launch validation... [tptp:execution] Initializing source locator... [tptp:execution] Launching delegate... [tptp:execution] Waiting.... [tptp:execution] Test result 'TestCMDBfRegistrationOperation.execution' collecte d. [tptp:execution] Test 'org.eclipse.cosmos.dc.cmdbf.services.tests\junits\TestCMD BfRegistrationOperation.testsuite' completed. [tptp:execution] Test 'org.eclipse.cosmos.dc.cmdbf.services.tests\junits\TestDer egistrationInputTransformer.testsuite' started. [tptp:execution] Preparing launch delegate... [tptp:execution] Performing pre-launch check... [tptp:execution] Performing final launch validation... [tptp:execution] Initializing source locator... [tptp:execution] Launching delegate... [tptp:execution] Waiting.... [tptp:execution] Test result 'TestDeregistrationInputTransformer.execution' coll ected. [tptp:execution] Test 'org.eclipse.cosmos.dc.cmdbf.services.tests\junits\TestDer egistrationInputTransformer.testsuite' completed.
I am integrating the test automation with our nightly build. Use ANT to run the tptp automation. You can find more info about the env in comments #54 and #55 I don't start the workbench at all. Every time the TPTP All in one is unzipped, a new workspace is created and test cases are extracted from CVS. So every test starts from scratch.
> eg: ant.bat -lib 45m6_ant -f 45_publish.xml -Dbuild_space=E:/Bobz/workarea/COSMOS/TestAuto/45_tmp >Folder 45m6_ant should contain: >ant-tptp.jar >com.ibm.icu_3.8.1.v20080402.jar >org.eclipse.osgi_3.4.0.v20080427-0830.jar >TestAuto.jar (will attach) >folder 45_test_setup should contain: >birt-report-framework-2_3_0-N20080515.zip >dtp-1.6RC1.zip >GEF-runtime-I200805121830.zip >org.eclipse.tptp.test.report.birt-TPTP-4.5.0-200805230100.zip >tptp.runtime.allInOne.win32.win32.x86-TPTP-4.5.0-200805230100.zip Bobby, I am trying to set up my Linux to reproduce this. But got couple of questions: 1. where can I get ant.bat and its Linux equivalent? 2. where should I build 45_test_setup directory? Any where under my $HOME?
(In reply to comment #110) > Bobby, I am trying to set up my Linux to reproduce this. But got couple of > questions: > > 1. where can I get ant.bat and its Linux equivalent? http://ant.apache.org/bindownload.cgi > 2. where should I build 45_test_setup directory? Any where under my $HOME? It should be in the TestAuto folder. You can create this folder anywhere. TestAuto should contain the following: 1) the test script (45_publish.xml) 2) apache-ant-1.7.0-bin (Download from internet) 3) Folder ant_lib, this should contain a) ant-tptp.jar copy from eclipse\plugins\org.eclipse.hyades.execution_* b) com.ibm.icu_*.jar copy from eclipse\plugins c) org.eclipse.osgi_*.jar copy from eclipse\plugins d) TestAuto.jar 4) Folder 45_test_setup, this should contain birt-report-framework-*.zip dtp_*.zip GEF-runtime-*.zip tptp.runtime.allInOne.*.zip org.eclipse.tptp.test.report.birt-TPTP-*.zip (TPTP BIRT Test Report plugin) you can download the test setup from http://www.eclipse.org/tptp/home/downloads/ 5) Folder Test_Results (Test reports are created here) I am attaching a file Cosmos_TestAuto_Linux.zip. It has the contents of ant_lib and a file 45_readme.txt with instructions. The build script will install TPTP from the 45_test_setup folder, download cosmos drivers and test cases automatically, run test cases and create test report.
Created attachment 108661 [details] Cosmos_TestAuto_Linux.zip Contains the basic folders in TestAuto, test script and a readme file with instructions
I set up my TestAuto directory and run the 45_run_auto.sh (after I modified it a little bit). The build was successful. I looked at the test results(index.html under Test_Results) and it showed that all but one have been completed though about one-third have failure rate > 0%. I've attached the build.log. I can attach test results if needed.
Created attachment 108672 [details] Bing's testlog from Ant build on Linux
Hi Bling, Looks like you got it to work. Did you use external RAC? Also which TPTP build did you use? Any special configuration reqd? Regarding the test failures, there were changes to build script, which I have included in the zip attached. But the results doesn't matter as long as we get execution to work.
Here are the files used to build the test environment: tptp.runtime.allInOne.linux.gtk.x86-TPTP-4.5.0.zip apache-ant-1.7.0-bin.tar (not 1.6.5) In ant_lib: ant-tptp.jar org.eclipse.osgi_3.4.0.v20080605-1900.jar com.ibm.icu_3.8.1.v20080530.jar TestAuto.jar In 45_test_setup: birt-report-framework-2_3_0.zip cosmos-rm-incubation-sdk-COSMOS-1.0.0-200807241123.zip cosmos-sdk-incubation-COSMOS-1.0.0-200807241123.zip dtp_1.6.0.zip GEF-runtime-3.4.0.zip org.eclipse.tptp.test.report.birt-TPTP-4.5.0.zip tptp.runtime.allInOne.linux.gtk.x86-TPTP-4.5.0.zip
Bobby, any update on this?
Created attachment 112711 [details] cosmos test automation setup We are automating COSMOS tptp junit. So far we are able to automate most of the JUnit, but in some test suites we are getting "inconclusive" result. Test execution file says class not found exception, but those classes are available in test project and getting builded in project's bin folder. Those classes are also available in <temp_dir>/<user>/<project>. For example "org.eclipse.cosmos.dc.cmdbf.services.tests" project contains total 9 test-suite but only one (TestCMDBfDeregistrationOperation) is not getting executed. When I open its execution record, i can see following message in it java.lang.ClassNotFoundException: org.eclipse.cosmos.dc.cmdbf.services.tests.internal.core.TestCMDBfDeregistrationOperation at java.lang.Class.forName(Class.java:163) at org.eclipse.hyades.test.java.runner.HyadesJUnitRunner.main(HyadesJUnitRunner.java:99) "org.eclipse.cosmos.dc.cmdbf.services.tests" project is available under Host : dev.eclipse.org Repository path : /cvsroot/technology Module : org.eclipse.cosmos/tests/data-collection/org.eclipse.cosmos.dc.cmdbf.services.tests Once the automation is over, I ran the same test-suite from within automation eclipse and it run successfully. I am attaching scripts and test automation setup here. You can set it up on your machine by following the instructions in "readme.html". Please let me know if any more information is required. thanks
(In reply to comment #118) Saurabh, this symptom is different than the original symptom for this defect. Please open a new defect under the TPTP ASF product and ASF.Runtime component. Bing: Saurabh is taking over for Bobby for the COSMOS test automation. He has seen the same symptoms as this defect.
Mass update of P1 enhancements and defects targetted to future to P2.
The TPTP BVTs are able to execute using ASF. Resolving.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
