On Wed, Oct 12, 2016 at 09:16:08PM +0300, Nir Soffer wrote:
> If you want to reproduce the errors, try this patch:
> https://gerrit.ovirt.org/65404
>
> On Wed, Oct 12, 2016 at 9:14 PM, Nir Soffer wrote:
> > Hi all,
> >
> > Trying to run vdsm tests via tox (so correct nose is used automatically),
Hi,
Jakub was right: the issue has been introduced with commit 221c7ed.
It affects just the dev env since there we are currently not installing (we
need to dig this!) DWH which instead is a dependency on the packaged builds
since 4.0.
Patch https://gerrit.ovirt.org/#/c/65409/ fixes it.
ciao
On
On Fri, Oct 7, 2016 at 10:44 PM, Yaniv Kaul wrote:
> I'm trying on FC24, using python-ovirt-engine-sdk4-4.1.0
> -0.0.20161003git056315d.fc24.x86_64 to add a DC, and failing - against
> master. The client is unhappy:
> File
> "/home/ykaul/ovirt-system-tests/basic-suite-master/test-scenarios/002_b
On Wed, Oct 12, 2016 at 9:14 PM, Nir Soffer wrote:
> Trying to run vdsm tests via tox (so correct nose is used automatically),
> some of the tests fail.
>
> The failure are all about ordering expectations, which look wrong.
tox -e tests
tests create: /vdsm/.tox/tests
tests installdeps: nose==1.3.
On Wed, Oct 12, 2016 at 9:14 PM, Nir Soffer wrote:
> 18:04:10 self.assertEquals(status.keys(), ['bricks', 'name'])
>
> status.keys() order is not undefined.
*is* undefined
(I was interrupted by a child while writing this)
___
Devel mailing list
Dev
If you want to reproduce the errors, try this patch:
https://gerrit.ovirt.org/65404
On Wed, Oct 12, 2016 at 9:14 PM, Nir Soffer wrote:
> Hi all,
>
> Trying to run vdsm tests via tox (so correct nose is used automatically),
> some of the tests fail.
>
> The failure are all about ordering expectati
Hi all,
Trying to run vdsm tests via tox (so correct nose is used automatically),
some of the tests fail.
The failure are all about ordering expectations, which look wrong.
Please check and fix your tests.
Thanks,
Nir
18:04:10 =
Same problem here.
Vojtech
- Original Message -
> From: "Dominik Holler"
> To: devel@ovirt.org
> Sent: Wednesday, October 12, 2016 2:39:27 PM
> Subject: Re: [ovirt-devel] engine-setup: ***L:ERROR Internal error: No module
> named dwh
>
> Hi,
> I got the same error. Is there any experi
Adding some relevant people.
On Wed, Oct 12, 2016 at 2:39 PM, Dominik Holler wrote:
> Hi,
> I got the same error. Is there any experience about this, by now?
> Dominik
>
> On Mon, 10 Oct 2016 15:48:08 -0400 (EDT)
> Jakub Niedermertl wrote:
>
> > Hi all,
> >
> > does anyone else experience follo
Hi,
I got the same error. Is there any experience about this, by now?
Dominik
On Mon, 10 Oct 2016 15:48:08 -0400 (EDT)
Jakub Niedermertl wrote:
> Hi all,
>
> does anyone else experience following error of `engine-setup`?
>
> $ ~/target/bin/engine-setup
> ***L:ERROR Internal error: No m
Fyi oVirt products maintainers,
An oVirt build for an official release is going to start right now.
If you're a maintainer for any of the projects included in oVirt
distribution and you have changes in your package ready to be released
please:
- bump version and release to be GA ready
- tag your re
- Original Message -
> From: "Francesco Romani"
> To: "devel"
> Sent: Wednesday, October 12, 2016 9:29:37 AM
> Subject: Re: [ovirt-devel] [vdsm] exploring a possible integration between
> collectd and Vdsm
>
> - Original Message -
> > From: "Yaniv Kaul"
> > To: "Francesco Roman
- Original Message -
> From: "Yaniv Kaul"
> To: "Francesco Romani"
> Cc: "devel"
> Sent: Tuesday, October 11, 2016 10:31:14 PM
> Subject: Re: [ovirt-devel] [vdsm] exploring a possible integration between
> collectd and Vdsm
>
> On Tue, Oct 11, 2016 at 2:05 PM, Francesco Romani
> wrote
13 matches
Mail list logo