dev@glassfish.java.net

RE: ABOUT DEPLOYMENT DEV TESTS

From: lvsongping <lvsongping_at_cn.fujitsu.com>
Date: Thu, 4 Apr 2013 17:06:31 +0900

Hi, Hong:

 

    Here attached some useful logs. From the log we can see the code of
Assert.assertTrue("BundleDescriptors do not
match.",dc.compareContent(bundleDescs[0], bundleDescs[1])); in
AnnotationTest.testDescriptors failed when it tests the ejb annotation and
inheritance annotation. I will check to see the exactly reason about this
later.

 

Thanks

 

Jeremy.

 

From: lvsongping [mailto:lvsongping_at_cn.fujitsu.com]
Sent: Thursday, April 04, 2013 3:58 PM
To: hong.hz.zhang_at_oracle.com
Cc: 'dev_at_glassfish.java.net'
Subject: RE: ABOUT DEPLOYMENT DEV TESTS

 

Hi, Hong:

 

   I got it. Maybe it is the windows specific issues. There is no directory
like ${env.APS_HOME}/modules, I think all of the related jars are moved to
the ${env.APS_HOME}/lib. The reason why it can be run in the environment of
LINUX is because it is no need to use the class called SpawnTask.

  I will look into the reason why there exists two failure cases on windows
platform.

 

Thanks

 

Jeremy

 

From: Hong Zhang [mailto:hong.hz.zhang_at_oracle.com]
Sent: Wednesday, April 03, 2013 10:27 PM
To: lvsongping
Cc: dev_at_glassfish.java.net
Subject: Re: ABOUT DEPLOYMENT DEV TESTS

 

Hi, Jeremy
    Our deployment dev tests hudson job is running successfully this morning
(all tests are passing), so this is either something windows specific or
related to your local changes. Maybe you can try to put both
(${env.APS_HOME}/modules and ${env.APS_HOME}/lib) on the classpath to see if
it makes a difference? This particular set of the tests are more unit test
like and use some GlassFish specific classes in the tests which might need
access to ${env.APS_HOME}/modules.

    Thanks,

- Hong

On 4/2/2013 10:57 PM, lvsongping wrote:

Hi Hong:

 

   I have run the dev tests right now and found two failures as follows:

 

Failure/total cases: 2/268

Environment: Windows 7

GlassFish Version: latest build version

 

[PASSED] AppClientAnnotationTest : testDescriptors,

[FAILED] EjbAnnotationTest : testDescriptors,

[FAILED] InheritanceAnnotationTest : testDescriptors,

[PASSED] WebAnnotationTest : testDescriptors,

 

 

From: lvsongping [mailto:lvsongping_at_cn.fujitsu.com]
Sent: Wednesday, April 03, 2013 11:36 AM
To: hong.hz.zhang_at_oracle.com
Cc: dev_at_glassfish.java.net
Subject: ABOUT DEPLOYMENT DEV TESTS

 

Hi, Hong:

 

   When I run the dev tests related to the deployment, I find the dev tests
can't be executed successfully when it run in the windows platform.

 

Here's some useful messages:

 

start-process-windows:

 

BUILD FAILED

E:\GF_MAIN\appserv-tests\devtests\deployment\config\common.xml:825: The
followin

g error occurred while executing this line:

E:\GF_MAIN\appserv-tests\devtests\deployment\config\common.xml:1011: The
followi

ng error occurred while executing this line:

E:\GF_MAIN\appserv-tests\devtests\deployment\config\common.xml:1291: The
followi

ng error occurred while executing this line:

E:\GF_MAIN\appserv-tests\devtests\deployment\config\common.xml:1303: taskdef
cla

ss SpawnTask cannot be found

 

So I have tried to find the SpawnTask and found the address is not correct.
So I have changed the classpath from "${env.APS_HOME}/modules" to
"${env.APS_HOME}/lib"

 

I will check to see whether the dev tests can be run successfully at the
windows platform.

 

 

Thanks

 

Jeremy