[jboss-dev] hudson JBoss-AS-5.1.x-testSuite-sun15 #208

[Jason T. Greene]

Ah, ok. That makes sense.

Flavia & Ståle,

If you guys decide to look into the GA problems, 
org.jboss.test.aop.test.TxLockUnitTestCase seems to highlight another 
issue. Although this is not critical if we can ship CR1 with AOP CR3.

Shelly McGowan wrote:
> 
> Jason,
> 
> I was working on the test jobs last night trying to get a dependable run.  The cmp tests 
> were failing becaue the "Deployers [were] Shutdown" (log output shown below).
> 
> Because the rest of the tests were timing out, I manually aborted the job.  
> 
> I did complete a test run locally with these results:
> 
> Number of tests run:   3786
> --------------------------------------------
> 
> Successful tests:      3753
> Errors:                21
> Failures:              12
> --------------------------------------------
> 
> With the revert of revert AOP to 2.1.0.CR3 the test current test run (job #209) is not showing this problem on
> Hudson.
> 
> 
> Shelly
> 
> 
> 
> 
> Running test:
> org.jboss.test.aop.test.TxLockUnitTestCase failed
> 
> output.log:
> 10:58:18,055 INFO  [TxLockTester] TESTING TX LOCK
> 10:58:19,101 ERROR [TxLockTester] failed
> java.lang.RuntimeException: TxLock didn't work.  2nd thread got there first.
> 	at java.lang.Thread.run(Thread.java:595)
> 11:03:11,170 INFO  [MainDeployer] deploy, url=file:/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.1.x-testSuite-sun15/JBossAS_5_x/testsuite/output/lib/aoptest.sar
> 11:03:11,193 WARN  [MainDeployer] Failed to deploy: file:/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.1.x-testSuite-sun15/JBossAS_5_x/testsuite/output/lib/aoptest.sar
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> 
> *** DEPLOYMENTS MISSING DEPLOYERS: Name
> 
> vfszip:/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.1.x-testSuite-sun15/JBossAS_5_x/testsuite/output/lib/aoptest.sar/
> 
> *** DEPLOYMENTS IN ERROR: Name -> Error
> 
> vfszip:/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.1.x-testSuite-sun15/JBossAS_5_x/testsuite/output/lib/aoptest.sar/ -> java.lang.IllegalStateException: vfszip:/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.1.x-testSuite-sun15/JBossAS_5_x/testsuite/output/lib/aoptest.sar/ is already installed.
> 
> 11:03:14,486 WARN  [DeployersImpl] Error during uninstall
> java.lang.Error: INTERNAL ERROR: context not found in previous state PostClassLoader context=name=vfszip:/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.1.x-testSuite-sun15/JBossAS_5_x/testsuite/output/lib/aoptest.sar/ state=PostClassLoader mode=Manual requiredState=ClassLoader
> 	at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:1204)
> 
> <snip>
> 12:01:53,440 WARN  [MainDeployer] Failed to deploy: file:/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.1.x-testSuite-sun15/JBossAS_5_x/testsuite/output/lib/cmp2-cmrtransaction.jar
> java.lang.IllegalStateException: Deployers are shutdown
> 	at org.jboss.deployers.plugins.deployers.DeployersImpl.checkShutdown(DeployersImpl.java:187)
> 
> 
> ----- Original Message -----
> From: "Jason T. Greene" <jason.greene at redhat.com>
> To: "JBoss.org development list" <jboss-development at lists.jboss.org>, "Alexey Loubyansky" <alexey.loubyansky at redhat.com>
> Sent: Friday, April 17, 2009 8:45:30 AM GMT -05:00 US/Canada Eastern
> Subject: Re: [jboss-dev] hudson JBoss-AS-5.1.x-testSuite-sun15 #208
> 
> Looks like the build failure was a hudson issue. The process was killed 
> when those tests failed
> 
> Jason T. Greene wrote:
>> Yeah you can get to the last log of the work space. It is big though, 
>> you probably want to wget it.
>>
>> http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.1.x-testSuite-sun15/ws/JBossAS_5_x/build/output/jboss-5.1.0.CR1/server/all/log/server.log 
>>
>>
>> Alexey Loubyansky wrote:
>>> There are a lot of CMP failed tests with the same cause. There must be 
>>> a deployment error. But I don't see it locally. Is there a way to get 
>>> to the server.log or could somebody who can reproduce the failure send 
>>> me the deployment error please?
>>>
>>> Thanks,
>>> Alexey
>>>
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development


-- 
Jason T. Greene
JBoss, a division of Red Hat