[jboss-jira] [JBoss JIRA] Assigned: (JBAS-5918) Hudson builds erroneously report builds as failed after ant upgrade

[Aleksandar Kostadinov (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksandar Kostadinov reassigned JBAS-5918:
-------------------------------------------

    Assignee: Aleksandar Kostadinov  (was: Rajesh Rajasekaran)


Oddly the issue doesn't appear when I execute only one target with few tests between start and stop. Anyways, the bug seems related to https://issues.apache.org/bugzilla/show_bug.cgi?id=41368

Should I care to try out the patch and go for patching the built-in ant, or just explain in the build.xml why the stop command is commented out?

> Hudson builds erroneously report builds as failed after ant upgrade
> -------------------------------------------------------------------
>
>                 Key: JBAS-5918
>                 URL: https://jira.jboss.org/jira/browse/JBAS-5918
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Dimitris Andreadis
>            Assignee: Aleksandar Kostadinov
>            Priority: Critical
>             Fix For: JBossAS-5.0.0.CR2
>
>
> After Scott upgraded the ant used in AS trunk from 1.6.5 to 1.7.1, all hudson testsuite builds are marked as failed, e.g.
> http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSuite-sun15/860/ 
> I've configured hudson to keep testsuite/output/tests.log & testsuite/output/log/test.log but they don't offer any useful information.
> In fact, testsuite/output/tests.log gets overwriten with useless info:
> 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)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira