[jboss-dev] Profile Service Tests

Scott Stark sstark at redhat.com
Mon Sep 1 16:57:30 EDT 2008


I'm going to look into our StopServerTask. I see jboss-test is setup to 
compile against ant 1.7.0 so I'm also trying that to see if there is any 
difference in behavior.

Dimitris Andreadis wrote:
> Dimitris Andreadis wrote:
>> Scott Stark wrote:
>>> I don't see this in the test runs, and the only box I have 
>>> reproduced a failure on is due to an inability of the client to 
>>> reuse the 4446 port, and so the client remoting layer fails to 
>>> startup its streaming port. Its not even getting to the point of 
>>> trying a deployment.
>>>
>>> I'm now looking into why the current runs are failing to shutdown:
>>>
>>> tests-report:
>>>      [tar] Building tar: 
>>> /Users/svn/JBossHead/jboss-head/testsuite/output/2008-08-31.21-39.tgz
>>>
>>> BUILD FAILED
>>> /Users/svn/JBossHead/jboss-head/testsuite/build.xml:969: Some 
>>> servers failed to shutdown cleanly.
>>>
>>> Total time: 179 minutes 36 seconds
>>> [589][valkyrie: testsuite]$
>>>
>>> I have reproduced this, but the server is in fact shutting down. The 
>>> last servers run are the cluster-profilesvc-0/1 configs, and their 
>>> logs show clean shutdowns. I guess we need more debug output from 
>>> the server task as to what it thinks is not shutting down.
>>
>> Scott, the server shutdown problem must be related to the ant 1.7.1 
>> upgrade:
>>
>> http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSuite-sun15/860/ 
>
>
> I created a jira for this annoying issue:
> https://jira.jboss.org/jira/browse/JBAS-5918
>
> I've configured hudson to keep some more logs but I don't understand 
> why testsuite/output/tests.log gets overwritten with the following:
>
> BUILD FAILED
>
> /qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-jrockit15/trunk/testsuite/build.xml:968: 
> Some servers failed to shutdown cleanly.
> at org.apache.tools.ant.taskdefs.Exit.execute(Exit.java:142)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
>
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
>
> at java.lang.reflect.Method.invoke(Method.java:585)
> at 
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) 
>
> at org.apache.tools.ant.Task.perform(Task.java:348)
> at org.apache.tools.ant.Target.execute(Target.java:357)
> at org.apache.tools.ant.Target.performTasks(Target.java:385)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
> at 
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) 
>
> at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
> at org.apache.tools.ant.Main.runBuild(Main.java:758)
> at org.apache.tools.ant.Main.startAnt(Main.java:217)
> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
>
> In my local run this file contains the test run output (i.e. what the 
> console would show, from
> <record name="output/tests.log" append="no" action="start" 
> loglevel="info"/>
> to
>       <antcall target="tests-report"/>
>       <record name="output/tests.log" action="stop"/>
>
> For some reason the following overwrites the file
>
>       <condition property="servers.shutdown.failed">
>          <and>
>             <not><isset property="servers.shutdown.nocheck"/></not>
>             <isfileselected file="output/tests.log">
>                <or>
>                   <contains text="Unable to shutdown server properly"/>
>                   <not><contains text="[server:stop]"/></not>
>                </or>
>             </isfileselected>
>          </and>
>       </condition>
>       <fail message="Some servers failed to shutdown cleanly."
>          if="servers.shutdown.failed"/>
>




More information about the jboss-development mailing list