8:15 a.m.
Yes, that's due to that file locking.
See my comment here:
- http://jira.jboss.com/jira/browse/JBAS-5625
DeploymentProgressImpl:
try
{
target.undeploy(deployment);
status = new SerializableDeploymentStatus(command,
StateType.COMPLETED);
status.setTarget(target);
status.setMessage("Completed undeploy for target: "+target);
status.setCompleted(true);
status.setRunning(true);
currentStatus = status;
event = new ProgressEvent(deployment, currentStatus);
notify(event);
}
catch(Exception e)
{
status = new SerializableDeploymentStatus(command,
StateType.FAILED);
status.setTarget(target);
status.setFailure(e);
status.setFailed(true);
currentStatus = status;
ProgressEvent error = new ProgressEvent(deployment,
currentStatus);
notify(error);
break;
}
}
So instead of complete == true, you get false, since target.undeploy
throws error not being able to delete file.
And the test asserts on complete == true.
Dimitris Andreadis wrote:
All I see on WinXP is:
<testcase
classname="org.jboss.test.profileservice.test.DeployUnitTestCase"
name="testWarDeployment" time="2.266">
<failure message="DeploymentStatus.isCompleted"
type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError:
DeploymentStatus.isCompleted
at
org.jboss.test.profileservice.test.DeployUnitTestCase.testDeployment(DeployUnitTestCase.java:131)
at
org.jboss.test.profileservice.test.DeployUnitTestCase.testWarDeployment(DeployUnitTestCase.java:139)
</failure>
</testcase>
<testcase
classname="org.jboss.test.profileservice.test.DeployUnitTestCase"
name="testEjb3xDeployment" time="1.375">
<failure message="DeploymentStatus.isCompleted"
type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError:
DeploymentStatus.isCompleted
at
org.jboss.test.profileservice.test.DeployUnitTestCase.testDeployment(DeployUnitTestCase.java:131)
at
org.jboss.test.profileservice.test.DeployUnitTestCase.testEjb3xDeployment(DeployUnitTestCase.java:155)
</failure>
</testcase>
<testcase
classname="org.jboss.test.profileservice.test.DeployUnitTestCase"
name="testEjb2xDeployment" time="1.75">
<failure message="DeploymentStatus.isCompleted"
type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError:
DeploymentStatus.isCompleted
at
org.jboss.test.profileservice.test.DeployUnitTestCase.testDeployment(DeployUnitTestCase.java:131)
at
org.jboss.test.profileservice.test.DeployUnitTestCase.testEjb2xDeployment(DeployUnitTestCase.java:172)
</failure>
</testcase>
<testcase
classname="org.jboss.test.profileservice.test.DeployUnitTestCase"
name="testEarDeployment" time="0.922">
<failure message="DeploymentStatus.isCompleted"
type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError:
DeploymentStatus.isCompleted
at
org.jboss.test.profileservice.test.DeployUnitTestCase.testDeployment(DeployUnitTestCase.java:131)
at
org.jboss.test.profileservice.test.DeployUnitTestCase.testEarDeployment(DeployUnitTestCase.java:191)
</failure>
</testcase>
<testcase
classname="org.jboss.test.profileservice.test.DeployUnitTestCase"
name="testMCBeansDeployment" time="0.156">
<failure message="DeploymentStatus.isCompleted"
type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError:
DeploymentStatus.isCompleted
at
org.jboss.test.profileservice.test.DeployUnitTestCase.testDeployment(DeployUnitTestCase.java:131)
at
org.jboss.test.profileservice.test.DeployUnitTestCase.testMCBeansDeployment(DeployUnitTestCase.java:197)
</failure>
</testcase>
<testcase
classname="org.jboss.test.profileservice.test.DeployUnitTestCase"
name="testSarDeployment" time="0.078">
<failure message="DeploymentStatus.isCompleted"
type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError:
DeploymentStatus.isCompleted
at
org.jboss.test.profileservice.test.DeployUnitTestCase.testDeployment(DeployUnitTestCase.java:131)
at
org.jboss.test.profileservice.test.DeployUnitTestCase.testSarDeployment(DeployUnitTestCase.java:203)
</failure>
Ales Justin wrote:
> What's your OS?
> Or what are the failures in DeployUTC (DUTC)?
>
> Since I've re-factored DUTC test to have few try/finally blocks,
> possibly cleaning up after failures.
>
> btw: how are these tests ordered?
> Randomly or alphabetically?
> If 2nd, let's rename DUTC to something starting with R or after.
> So we at least get relevant results on other tests.
>
> Is ClusteredDUTC even functional?
>
> Dimitris Andreadis wrote:
>> Scott Stark wrote:
>>> How do you run the tests?
>>
>> The very latest I see is:
>>
>> build tests-profileservice
>> Calling ..\tools\bin\ant.bat tests-profileservice
>> Buildfile: build.xml
>> ...
>> tests-profileservice:
>> [delete] Deleting directory
>> X:\cvs\jboss-public\jboss-head\build\output\jboss
>> -5.0.0.CR1\server\profileservice
>> [echo] creating profileservice config,
>> jboss.dist=X:\cvs\jboss-public\jboss
>> -head\build\output\jboss-5.0.0.CR1
>> [copy] Copying 363 files to
>> X:\cvs\jboss-public\jboss-head\build\output\jbo
>> ss-5.0.0.CR1\server\profileservice
>> [copy] Copying 1 file to
>> X:\cvs\jboss-public\jboss-head\build\output\jboss-
>> 5.0.0.CR1\server\profileservice\conf
>> [copy] Copying 1 file to
>> X:\cvs\jboss-public\jboss-head\build\output\jboss-
>> 5.0.0.CR1\server\profileservice\deployers
>> [echo] Overwriting config descriptors
>> [copy] Copying 1 file to
>> X:\cvs\jboss-public\jboss-head\build\output\jboss-
>> 5.0.0.CR1\server\profileservice
>> [server:start] Starting server "profileservice" with command:
>> [server:start] C:\home\tools\jdk1.5.0_09\bin\java -cp
>> X:\cvs\jboss-public\jboss-
>> head\build\output\jboss-5.0.0.CR1\bin\run.jar;c:\home\tools\jdk1.5.0_09\lib\tool
>>
>> s.jar -Xms128m -Xmx512m -XX:MaxPermSize=512m
>> -XX:+HeapDumpOnOutOfMemoryError -Dj
>> ava.net.preferIPv4Stack=true
>> -Djava.endorsed.dirs=X:\cvs\jboss-public\jboss-head
>> \build\output\jboss-5.0.0.CR1/lib/endorsed -Djgroups.udp.ip_ttl=0
>> org.jboss.Mai
>> n -c profileservice -b localhost
>> [echo] Starting patternset=profileservice.includes
>> config=profileservice
>> [junit] Running
>> org.jboss.test.profileservice.test.DeployUnitTestCase
>> [junit] Tests run: 6, Failures: 6, Errors: 0, Time elapsed:
>> 12.047 sec
>> [junit] Test
>> org.jboss.test.profileservice.test.DeployUnitTestCase FAILED
>> [junit] Running
>> org.jboss.test.profileservice.test.JmsDestinationUnitTestCase
>> [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 3.969
>> sec
>> [junit] Running
>> org.jboss.test.profileservice.test.ProfileServiceUnitTestCase
>> [junit] Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 6.89
>> sec
>> [server:stop] Shutting down server: profileservice
>> [server:stop] Shutting down server:
>> C:\home\tools\jdk1.5.0_09\bin\java -cp X:\cv
>> s\jboss-public\jboss-head\build\output\jboss-5.0.0.CR1\bin\shutdown.jar;X:\cvs\j
>>
>> boss-public\jboss-head\build\output\jboss-5.0.0.CR1\client\jbossall-client.jar;X
>>
>> :\cvs\jboss-public\jboss-head\build\output\jboss-5.0.0.CR1\client\jboss-common.j
>>
>> ar org.jboss.Shutdown --server jnp://localhost:1099 --shutdown
>> [server:stop] shutdownTimeout will be=45
>>
>> BUILD SUCCESSFUL
>> Total time: 3 minutes 4 seconds
>> _______________________________________________
>> 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
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development