[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-5864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

sebastien goasguen updated CLOUDSTACK-5864:
-------------------------------------------

    Affects Version/s: 4.2.1

> Simulator profile broken 
> -------------------------
>
>                 Key: CLOUDSTACK-5864
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5864
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: marvin
>    Affects Versions: 4.2.1, 4.3.0
>            Reporter: sebastien goasguen
>            Priority: Blocker
>
> When running the simulator we use the marvin.setup profile:
> mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/basic.cfg -pl 
> :cloud-marvin integration-test
> Recent argument changes in deployAndrun.py broke this profile in 
> tools/marvin/pom.xml
> <executions>
>               <execution>
>                 <id>pre-integration-test</id>
>                 <phase>pre-integration-test</phase>
>                 <goals>
>                   <goal>exec</goal>
>                 </goals>
>                 <configuration>
>                   <workingDirectory>${basedir}/marvin</workingDirectory>
>                   <executable>python</executable>
>                   <arguments>
>                     <argument>deployAndRun.py</argument>
>                     <argument>-c</argument>
>                     <argument>${resolved.userdir}/${marvin.config}</argument>
>                     <argument>-t</argument>
>                     <argument>/tmp/t.log</argument>
>                     <argument>-r</argument>
>                     <argument>/tmp/r.log</argument>
>                     <argument>-f</argument>
>                     
> <argument>${resolved.basedir}/marvin/testSetupSuccess.py</argument>
>                   </arguments>
>                 </configuration>
>               </execution>
>             </executions>



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to