I have never tested it on a machine which doesn't have libvirt, i'll get
back to you on that.
I've ran "tox -v -epy27" and it produced this ouput
> --
> Ran 0 tests in 0.001s
> OK
> ___
Run:
sudo pip install tox
And you will get the tox command.
Does ./run_tests.sh -N nova.tests.test_libvirt work fine when you
_don't_ have libvirt? It needs to skip the test if you don't have
libvirt installed, and it needs to run it and pass if you do.
Jenkins is going to run "tox -v -epy27"
Running with " ./run_tests.sh -N nova.tests.test_libvirt" works just fine,
however i don't know if this is enough to get it past jenkins :/
On Mon, Jul 2, 2012 at 3:26 PM, Daniel P. Berrange wrote:
> On Mon, Jul 02, 2012 at 01:43:31PM +0100, Leander Bessa Beernaert wrote:
> > So, if no system pac
On Mon, Jul 02, 2012 at 01:43:31PM +0100, Leander Bessa Beernaert wrote:
> So, if no system packages can be imported, how do you test the "connection"
> class for the libvirt driver?
>
> How does that particular test case wrap around the fact that it requires
> the libvirt module? The only thing i
@Jay Thx.
@Monty I'm unable to run "tox -efull", it keeps saying the command could
not be located. I'm supposed to run this from the same place i run
"run_tests.sh" right?
On Mon, Jul 2, 2012 at 2:08 PM, Jay Pipes wrote:
> On 07/02/2012 08:57 AM, Leander Bessa Beernaert wrote:
> > I'm developin
On 07/02/2012 08:57 AM, Leander Bessa Beernaert wrote:
> I'm developing on custom branch and haven't updated the repository for
> at least 3 weeks.
> Do i fetch the lastest changes like this:
>
> git remote update
> git checkout master
> git pull origin master
>
> git checkout
I'm developing on custom branch and haven't updated the repository for at
least 3 weeks.
Do i fetch the lastest changes like this:
> git remote update
> git checkout master
> git pull origin master
git checkout
git pull master
?
On Mon, Jul 2, 2012 at 1:44 PM, Monty Taylor wrote:
>
>
> On 0
On 07/02/2012 08:43 AM, Leander Bessa Beernaert wrote:
> So, if no system packages can be imported, how do you test the
> "connection" class for the libvirt driver?
We're working on that - but as I said, please try running tox -efull
which _should_ run tests with libvirt support enabled.
> How
So, if no system packages can be imported, how do you test the "connection"
class for the libvirt driver?
How does that particular test case wrap around the fact that it requires
the libvirt module? The only thing i could find are these lines of code in
the driver's __init__ method. Do these someh
On 07/02/2012 06:02 AM, Leander Bessa Beernaert wrote:
> Thanks, that let me see the real problem now:
>
> ./tools/with_venv.sh nosetests -svx nova
> nose.config: INFO: Set working dir to /home/gsd/nova/nova/tests
> nose.config: INFO: Working directory /home/gsd/nova/nova/tests is a
Thanks, that let me see the real problem now:
> ./tools/with_venv.sh nosetests -svx nova
> nose.config: INFO: Set working dir to /home/gsd/nova/nova/tests
> nose.config: INFO: Working directory /home/gsd/nova/nova/tests is a
> package; adding to sys.path
> nose.config: INFO: Ignoring files matchin
Hi Leander,
I've noticed some weirdness with the openstack.nose_plugin (which is
used by default for the Nova test runner) sometimes either throwing
errors (particularly errors raised by nosetests) away and/or coming up
with a different set of skip tests than when running just with nosetests.
Hello,
I'm sorry to restart the topic (
https://lists.launchpad.net/openstack/msg13621.html), but
i accidentally deleted the message in my inbox :S.
I'm still having the same problem, each time i add "import libvirt" to the
file "diangostics.py" (https://review.openstack.org/#/c/8839/) the entire
13 matches
Mail list logo
