With a slightly increased deploy-wait timeout it's passing. Maybe with the new setup
the
timing of the test changed?
Scott, couldn't you pick up a sorter name? ;-)
profileservice-hdscanner-jboss-beans.xml
Dimitris Andreadis wrote:
I think this latest run also present this problem of the minimal
config
not shutting down.
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
I've verified that locally using the 'build jboss-minimal-tests',
although another manual test I did deploying/undeploying 'shutdown.sar'
seemed to work.
Scott Stark wrote:
> It was just that the HDScanner bean was being deployed differently
> based on the profile service implementation. Now the HDScanner bean is
> deployed as deploy/profileservice-hdscanner-jboss-beans.xml in every
> profile independent of which profile service implementation is used.
>
> Scott Stark wrote:
>> The immediate problem that shows up is that hot deployment is not
>> working, so the tests don't run because the minimal configuration
>> requires this in order to shutdown. Its failure to shutdown causes
>> the testsuite run to fail because the naming ports are still active
>> when the all configuration is started.
>>
>>
https://jira.jboss.org/jira/browse/JBAS-6190
>>
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development