|
| Re: Custom Test Execution (perl) + RAC 4.2 Deployment problem ? [message #85225 is a reply to message #84921] |
Thu, 12 October 2006 21:31   |
 Joe Toomey
Messages: 79
Registered: July 2009 |
Member |
|
|
Johan Andersson wrote:
> Hi
> I have downloaded the perl Custom Test Execution example from Testing Tool
> Project, deployed the plugins on the RAC and made changes to the config.xml
> file. I have also followed the tips in:
> 8 juni 2006 14:45<jptoomey@us.ibm.com> wrote in message
> news:<e6964s$m25$1@utils.eclipse.org>
>
> My test execution is very slow and seems to be halting at Executing test:
> 93%
>
> I think im missing something in my deployment on the RAC, has anyone
> experienced a similar problem? or have any suggestions ?
> I have added:
> <Variable name="CLASSPATH_ORG_ECLIPSE_HYADES_TEST_TOOLS_CORE"
> position="append"
> value=" C:\RAServerLatest\tptp\tptpdc\win_ia32\plugins\org.eclipse.h yades.test.tools.core_4.2.1.v200607310100\perl.runner.jar "/>
>
> <Variable name="CLASSPATH_ORG_ECLIPSE_HYADES_TEST_TOOLS_CORE"
> position="append"
> value=" C:\RAServerLatest\tptp\tptpdc\win_ia32\plugins\org.eclipse.h yades.test.tools.core_4.2.1.v200607310100\hexperl.jar "/>
>
> to the config.xml file in the
> org.eclipse.hyades.test.tools.core_4.2.1.v200607310100/confi g directory and
> the .jar files in the root of
> org.eclipse.hyades.test.tools.core_4.2.1.v200607310100 ´directory.
>
> Im using:
>
> Windows XP
> Eclipse 3.2
> TPTP 4.2
> RAC 4.2
>
> Brgds Johan
>
>
Hi Johan,
This is caused by a regression from the fix for
https://bugs.eclipse.org/bugs/show_bug.cgi?id=84790 . After your
executable object adapter sets the jvm arguments, they are further
modified to include the name of the test agent that the workbench should
look for. In the fix for 84790, the way in which the agent name is
added to the jvm arguments changed, and although the fix appears to have
been written to work properly with test types that pass their runner
arguments positionally, it in fact does not work.
The easiest way to fix this is to pass your script name in a
specifically named jvm property like this:
protected final String TEST_CLASS = "hyades.runner.testClass";
....
jvmArgs += "-D" + TEST_CLASS +"=\"" + theImplementor.getResource() + "\"";
jvmArgs += "org.eclipse.hyades.test.perl.runner.HyadesPerlRunner";
and then read the script name from that jvm property name in the runner
like this:
....
private void runTest(String[] args) {
try {
runnerStarted();
String perlScript = System.getProperty("hyades.runner.testClass");
if ( perlScript == null )
{
logVerdict("No script specified", VerdictEvent.VERDICT_ERROR);
throw new Exception();
}
String cmdArray[] = {"perl", perlScript};
....
I have filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=160757 to
track fixing the overall problem, and I have ammended the ported 4.2
code on the TPTP website with the suggestions I made above.
http://www.eclipse.org/tptp/test/documents/tutorials/eclipse Con2005/ImprovedEclipseConDemo_ported_TPTP42.zip
Thanks for identifying the issue.
--Joe
|
|
|
|
Powered by
FUDForum. Page generated in 0.04144 seconds
] 
Search
Help
Register
Login
Home
