[jbossts-issues] [JBoss JIRA] (JBTM-1693) TXFramework Tests: Arquillian DeploymentException: Cannot deploy: test.war
Paul Robinson (JIRA)
jira-events at lists.jboss.org
Thu May 16 03:53:06 EDT 2013
[ https://issues.jboss.org/browse/JBTM-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Robinson reassigned JBTM-1693:
-----------------------------------
Assignee: Amos Feng (was: Paul Robinson)
Amos,
Can you take a look at this today? It's pretty important as it's breaking our CI. If it is caused by a change in WildFly, you will probably find "git bisect" to be a useful tool for detecting which commit caused it. Here'a a tutorial that I found useful:
http://code-worrier.com/blog/git-bisect-basics/
> TXFramework Tests: Arquillian DeploymentException: Cannot deploy: test.war
> --------------------------------------------------------------------------
>
> Key: JBTM-1693
> URL: https://issues.jboss.org/browse/JBTM-1693
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing, TXFramework
> Reporter: Paul Robinson
> Assignee: Amos Feng
> Priority: Critical
> Fix For: 5.0.0.M3
>
>
> See:
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/48/TESTS=XTS,jdk=jdk7.latest,label=linux/console
> Looks like a general issue with our usage of Arquillian. It seems to be happening consistently, so should be easy to reproduce. It's just started happening and I don't think we have made any changes that could of caused it, therefore I suspect it's due to some change in WildFly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbossts-issues
mailing list