[
https://issues.apache.org/jira/browse/CLOUDSTACK-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458965#comment-13458965
]
Rohit Yadav commented on CLOUDSTACK-136:
----------------------------------------
It was a chown issue. Somehow jenkins folders had root user. So, we chown'd
~/.m2 and jenkins workspace folder. It works now.
> unit test failing on axis-deploy
> --------------------------------
>
> Key: CLOUDSTACK-136
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-136
> Project: CloudStack
> Issue Type: Bug
> Components: Test
> Affects Versions: pre-4.0.0
> Reporter: David Nalley
> Assignee: Rohit Yadav
> Priority: Critical
> Fix For: pre-4.0.0
>
>
> Unit tests for 4.0 are failing at the deploy-axis stage:
> See: http://jenkins.cloudstack.org/job/test-junit-4.0
> deploy-axis:
> BUILD FAILED
> /var/lib/jenkins/workspace/test-junit-4.0/build/build-aws-api.xml:174: src
> '/var/lib/jenkins/workspace/test-junit-4.0/deps/awsapi-lib/axis2-webapp-1.5.1.war'
> doesn't exist.
> Total time: 5 minutes 2 seconds
> Build step 'Invoke Ant' marked build as failure
> Archiving artifacts
> Recording test results
> Performance: Percentage of errors greater or equal than 0% sets the build as
> unstable
> Performance: Percentage of errors greater or equal than 0% sets the build as
> failure
> Performance: Recording JUnit reports 'unittest/TEST-*.xml'
> Sending e-mails to: cloudstack-comm...@incubator.apache.org
> murali.re...@citrix.com chip.child...@gmail.com t...@apache.org
> alena.prokharc...@citrix.com disheng...@gmail.com w...@widodh.nl
> alex.hu...@citrix.com sudi...@gmail.com nitin.me...@citrix.com
> sheng.y...@citrix.com edi...@citrix.com jessica.w...@citrix.com
> pra...@cloud.com mice_...@tcloudcomputing.com agneya2...@yahoo.com
> chirad...@apache.org brian.fede...@citrix.com anth...@cloud.com
> pranav.sax...@citrix.com da...@gnsa.us frank.zh...@citrix.com
> build-cloudstack-4.0-rhel6.3 is disabled. Triggering skipped
> Finished: FAILURE
--
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
