Yes, mvn -Pdeveloper,marvin.test is trying to create the same zone created by marvin.setup.
Also, mvn -Pdeveloper,marvin.setup ran tests after the zone was setup. 3 tests were run and 1 test i.e. TestDeployVM failed. I have attached the logs. Thank you, Likitha >-----Original Message----- >From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com] >Sent: Tuesday, April 09, 2013 3:05 PM >To: dev@cloudstack.apache.org >Subject: Re: [MERGE] bvt branch to master > > > >On 4/9/13 12:57 PM, "Chiradeep Vittal" <chiradeep.vit...@citrix.com> wrote: > >>Doesn't work for me >>A. -Dmarvin.config=setup/dev/advanced.cfg needs absolute path for some >>reason B. [INFO] --- exec-maven-plugin:1.2.1:exec (integration-test) @ >>cloud-marvin --- >>Usage: nosetests [options] >> >>nosetests: error: no such option: --with-marvin >> > >OK, 'B' got resolved by re-installing Marvin. > >New problem: >mvn -Pdeveloper,marvin.test complains that the zone is already created. >It seems to be creating the same zone created by marvin.setup >
