cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chip Childers <chip.child...@sungard.com>
Subject Re: [PROPOSAL] BVT for CloudStack checkins
Date Fri, 22 Mar 2013 20:19:03 GMT
On Fri, Mar 22, 2013 at 01:07:48PM -0700, Chiradeep Vittal wrote:
> 
> 
> On 3/22/13 12:49 PM, "Chip Childers" <chip.childers@sungard.com> wrote:
> 
> >
> >
> >After running through the steps, I get this error:
> >
> >  mvn -Pdeveloper,marvin -Dmarvin.config=setup/dev/advanced.cfg -pl
> >:cloud-marvin integration-test
> >  ERROR: transport error 202: bind failed: Address already in use
> >  ERROR: JDWP Transport dt_socket failed to initialize,
> >TRANSPORT_INIT(510)
> >  JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports
> >initialized [../../../src/share/back/debugInit.c:741]
> >  FATAL ERROR in native method: JDWP No transports initialized,
> >jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
> >  [1]    28712 abort (core dumped)  mvn -Pdeveloper,marvin
> >-Dmarvin.config=setup/dev/advanced.cfg -pl
> >
> >
> >I think that running the jetty server from mvn may be problematic, if
> >steps
> >afterward are also going to require maven.  Is there a config to get
> >around this?
> 
> It looks like two java processes are being started up, and each want to
> bind to the same debug port. Both probably have something like -
> -Xrunjdwp:transport=dt_socket,address=8787,
> 
> Perhaps leave it out of MAVEN_OPTS?
> 
>

Yup.. I completely forgot that I had a debug port set.  Damn.

OK - Next errors:

mvn -Pdeveloper,marvin -Dmarvin.config=setup/dev/advanced.cfg -pl :cloud-marvin integration-test
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache CloudStack marvin 4.2.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- exec-maven-plugin:1.2.1:exec (generate-sources) @ cloud-marvin ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-marvin ---
[INFO] 
[INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @ cloud-marvin ---
[INFO] 
[INFO] --- exec-maven-plugin:1.2.1:exec (pre-integration-test) @ cloud-marvin ---
[INFO] 
[INFO] --- exec-maven-plugin:1.2.1:exec (integration-test) @ cloud-marvin ---
Usage: nosetests [options]

nosetests: error: no such option: --with-marvin
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:18.998s
[INFO] Finished at: Fri Mar 22 20:11:51 GMT 2013
[INFO] Final Memory: 23M/214M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (integration-test)
on project cloud-marvin: Command execution failed. Process exited with an error: 2 (Exit value:
2) -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following
articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException


Mime
View raw message