cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daan Hoogland <daan.hoogl...@gmail.com>
Subject Re: running BVT locally
Date Tue, 13 Aug 2013 07:48:27 GMT
my pip got corrupted, i reinstalled it.
python is installed with cygwin, it seems to work fine otherwise. I am
reinstalling cygwin as 64 bit version now and will let you know my
progress.

from eclipse cygwin is not going to help anyhow, is it?

regards,
Daan

On Tue, Aug 13, 2013 at 7:40 AM, Prasanna Santhanam <tsp@apache.org> wrote:
> Did you happen to take a look at the instructions for setting up a
> cygwin environment?
>
> https://cwiki.apache.org/confluence/x/gI7lAQ
>
> On Tue, Aug 13, 2013 at 11:04:08AM +0530, Prasanna Santhanam wrote:
>> Did you install Python in Cygwin's environment or on Windows? The
>> latter will not work since cygwin does not detect the python version
>> on your windows environment.
>>
>> On Mon, Aug 12, 2013 at 06:57:08PM +0200, Daan Hoogland wrote:
>> > Prasanna,
>> >
>> > I checked out the marvin and tst setuyp pages.
>> >
>> > I have marvin
>> >
>> > $ python
>> > Python 2.7.3 (default, Dec 18 2012, 13:50:09)
>> > [GCC 4.5.3] on cygwin
>> > Type "help", "copyright", "credits" or "license" for more information.
>> > >>> import marvin;
>> > >>> marvin
>> > <module 'marvin' from
>> > '/usr/lib/python2.7/site-packages/Marvin-0.1.0-py2.7.egg/marvin/__init__.pyc'>
>> > >>>
>> >
>> > but still
>> >
>> > $ nosetests --with-marvin --marvin-config=setup/dev/local.cfg -a
>> > tags="advanced" test/integration/smoke --load
>> > Usage: nosetests [options]
>> >
>> > nosetests: error: no such option: --with-marvin
>> >
>> > which seems correct because
>> >
>> > dhoogland@SBPLT101 /cygdrive/c/Users/dhoogland/cloudstack/cloudstack
>> > $ nosetests -p
>> > Plugin capture
>> > Plugin failuredetail
>> > Plugin xunit
>> > Plugin deprecated
>> > Plugin skip
>> > Plugin multiprocess
>> > Plugin logcapture
>> > Plugin coverage
>> > Plugin attributeselector
>> > Plugin doctest
>> > Plugin profile
>> > Plugin id
>> > Plugin allmodules
>> > Plugin collect-only
>> > Plugin isolation
>> > Plugin pdb
>> >
>> > So I try to build marvin but then I get
>> >
>> > [INFO] BUILD FAILURE
>> > [INFO] ------------------------------------------------------------------------
>> > [INFO] Total time: 1.938s
>> > [INFO] Finished at: Mon Aug 12 18:38:35 CEST 2013
>> > [INFO] Final Memory: 19M/181M
>> > [INFO] ------------------------------------------------------------------------
>> > [ERROR] Failed to execute goal
>> > org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (generate-sources) on
>> > project cloud-marvin: Command execution failed. Cannot run program
>> > "python" (in directory
>> > "C:\Users\dhoogland\cloudstack\cloudstack\tools\marvin\marvin"):
>> > CreateProcess error=2, The system cannot find the file specified ->
>> > [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
>> >
>> > even though
>> >
>> > $ python
>> > Python 2.7.3 (default, Dec 18 2012, 13:50:09)
>> > [GCC 4.5.3] on cygwin
>> > Type "help", "copyright", "credits" or "license" for more information.
>> > >>>
>> >
>> > Is this a windows thing? or is there some specific path coded
>> > somewhere for python?
>> >
>> > regards,
>> >
>> > On Mon, Aug 12, 2013 at 6:25 PM, Prasanna Santhanam <tsp@apache.org> wrote:
>> > > On Mon, Aug 12, 2013 at 06:20:58PM +0200, Daan Hoogland wrote:
>> > >> A bit of a stupid question, I guess
>> > >>
>> > >> On Mon, Aug 12, 2013 at 5:43 PM, Prasanna Santhanam <tsp@apache.org>
wrote:
>> > >> ...
>> > >> > I'll assume you have cloudstack setup manually and just want to
fire
>> > >> > all the tests against this deployment. This could be your laptop
from
>> > >> > where you have your management server running. Just open up the
integration
>> > >> > port 8096. All tests run on 8080 but the 8096 is required for
setting up
>> > >> > api/secret keys
>> > >> What does just open up 8096 mean, given I am running in jetty in
>> > >> eclipse? Should I edit some cfg or add params to the run?
>> > >>
>> > > If it's the dev environment, then you're good to go. port 8096 is the
>> > > port where system user interacts. It is closed by default for binary
>> > > installs but open on the dev environment.
>> > >
>> > >> ...
>> > >> > Most of the details of running tests is explained in the documentation.
Let me
>> > >> > know if anything is missing and I'll fix that up.
>> > >> without saying
>> > >>
>> > >> thanks,
>> > >
>> > > --
>> > > Prasanna.,
>> > >
>> > > ------------------------
>> > > Powered by BigRock.com
>> > >
>>
>> --
>> Prasanna.,
>>
>> ------------------------
>> Powered by BigRock.com
>
> --
> Prasanna.,
>
> ------------------------
> Powered by BigRock.com
>

Mime
View raw message