Re: [ovirt-devel] How to debug NullPointerException for project restapi-def inition of version 3.6.4.1?

[Kai Kang]

On Wed, Apr 6, 2016 at 6:03 PM, Juan Hernández  wrote:

> On 04/06/2016 11:51 AM, Kai Kang wrote:
> > Hi,
> >
> > I am building ovirt-engine 3.6.4.1 and failed with NullPointerException.
> > I build for cross compile with commands:
> >
> >
> >
> >
> tmp_repo=/buildarea3/kkang/builds/Mar31-ovrit-engine/bitbake_build/tmp/work/corei7-64-wrs-linux/ovirt-engine/3.6.4.1-r0/repo
> > export MAVEN_OPTS="-Dmaven.repo.local=$tmp_repo"
> >
> > makeEXTRA_BUILD_FLAGS="-s
> >
> /buildarea3/kkang/builds/Mar31-ovrit-engine/bitbake_build/tmp/work/corei7-64-wrs-linux/ovirt-engine/3.6.4.1-r0/settings.xml
> > --debug --offline"-j1 BUILD_GWT=1 BUILD_LOCALES=0
> > BUILD_UT=1  BUILD_VALIDATION=0
> >  JAVA_DIR=/usr/share/ovirt-engine/java   LOCALSTATE_DIR=/var
> > MAVENPOM_DIR=/usr/share/ovirt-engine/maven-poms PREFIX=/usr
> > SYSCONF_DIR=/etcPKG_SYSCONF_DIR=/etc/ovirt-engine
> > PKG_DOC_DIR=/usr/doc/ovirt-engine
> > PKG_EAR_DIR=/usr/share/ovirt-engine/engine.ear
> >  PKG_PKI_DIR=/etc/pki/ovirt-engine
> > PKG_JBOSS_MODULES=/usr/share/ovirt-engine/modules
> > PKG_CACHE_DIR=/var/cache/ovirt-engine
> > PKG_LOG_DIR=/var/log/ovirt-engine
> > PKG_TMP_DIR=/var/tmp/ovirt-engine
> > PKG_STATE_DIR=/var/lib/ovirt-engine PKG_USER=ovirt  PKG_GROUP=ovirt
> >  all
> >
> >
> > The error messages show:
> >
> > [INFO] oVirt Engine API Definition ... FAILURE
> [1.476s]
> > ...
> > [INFO]
> > 
> > [ERROR] Failed to execute goal
> > org.codehaus.mojo:exec-maven-plugin:1.2:java (default) on project
> > restapi-definition: An exception occured while executing the Java class.
> > null: InvocationTargetException: NullPointerException -> [Help 1]
> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> > execute goal org.codehaus.mojo:exec-maven-plugin:1.2:java (default) on
> > project restapi-definition: An exception occured while executing the
> > Java class. null
> > at
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> > ...
> > at javax.xml.bind.JAXB.marshal(JAXB.java:332)
> > at
> > org.ovirt.engine.api.rsdl.RsdlManager.serializeRsdl(RsdlManager.java:134)
> > at
> >
> org.ovirt.engine.api.rsdl.RsdlManager.generateRsdlFile(RsdlManager.java:84)
> > at
> org.ovirt.engine.api.rsdl.RsdlManager.main(RsdlManager.java:58)
> > ... 6 more
> >
> >
> > My questions are:
> >
> > 1 I know the error occurs in
> > file
> backend/manager/modules/restapi/interface/definition/src/main/java/org/ovirt/engine/api/rsdl/RsdlManager.java,
> > but how to debug it?
> >
> > 2 When I remove pom and jar files of javax.xml.bind.JAXB in mave repo
> > with offline mode, it still could find the class.
> > Which javax.xml.bind.JAXB is used? I searched the ovirt engine repo but
> > didn't find it either.
> >
>
> The version of JAXB used by that area of the code is the version of JAXB
> included in the JDK that you are using for the build. So the question is
> what version of the JDK are you using?
>

Hi Juan,

I am using icedtea7 to build openjdk-7. And I found the JAXB file.

Would you like to give some advice how to debug this issue? Does jdb could
debug such code?

Thanks a lot.

--Kai


>
> --
> Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
> 3ºD, 28016 Madrid, Spain
> Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [vdsm] Running VDSM unit tests on Travis CI using Docker

[Martin Sivak]

> Afaik, you won't be able to run any tests that touch networking, or kernel
> modules (bonding and such). That is as much a limitation of travis as of
> docker, that was one of the points why we started using chroots instead of
> docker containers on ovirt ci.

You might be able to ask for the old architecture - standard or trusty
- where you can do a bit more.

https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments

Martin

On Wed, Apr 6, 2016 at 1:23 PM, David Caro  wrote:
> On 04/06 14:19, Edward Haas wrote:
>> On Wed, Apr 6, 2016 at 1:41 PM, Milan Zamazal  wrote:
>>
>> > Edward Haas  writes:
>> >
>> > > On Wed, Apr 6, 2016 at 11:39 AM, Milan Zamazal 
>> > wrote:
>> > >
>> > > Thank you, Edward, this is useful not only for CI. I use docker for
>> > > building Vdsm and running its unit tests and this helped me to get
>> > the
>> > > proper updated set of packages after recent changes in Vdsm.
>> > >
>> > > BTW, it seems that the following packages should be additionally
>> > added
>> > > for `make check-all': psmisc, which, python-ioprocess
>> > >
>> > >
>> > > Are you saying that make check is passing on your local machine?
>> >
>> > When I add the packages given above, `make check-all' (as well as `make
>> > check') works for me except for 4 tests in lib/vdsm/schedule.py that
>> > produce the following errors with `make check-all':
>> >
>> > File "/home/pdm/ovirt/vdsm/vdsm-test/lib/vdsm/schedule.py", line 134,
>> > in schedule
>> >   heapq.heappush(self._calls, (deadline, call))
>> >   nose.proxy.TypeError: unorderable types: ScheduledCall() <
>> > ScheduledCall()
>> >
>> > File "/home/pdm/ovirt/vdsm/vdsm-test/tests/scheduleTests.py", line
>> > 160, in test_latency
>> >   med = ticker.latency[len(ticker.latency) / 2]
>> >   nose.proxy.TypeError: list indices must be integers, not float
>> >
>> > Those are probably Python 3 failures that should be fixed in Vdsm.
>> > The docker environment works fine for running the unit tests on my
>> > machine.
>> >
>>
>> I ran it on Travis CI with your recommended addition, and I am getting this
>> result: FAILED (SKIP=107, errors=14):
>> You can view the run here: https://travis-ci.org/EdDev/vdsm/builds/121117253
>
>
> Afaik, you won't be able to run any tests that touch networking, or kernel
> modules (bonding and such). That is as much a limitation of travis as of
> docker, that was one of the points why we started using chroots instead of
> docker containers on ovirt ci.
>
>
>> ___
>> Devel mailing list
>> Devel@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>
>
> --
> David Caro
>
> Red Hat S.L.
> Continuous Integration Engineer - EMEA ENG Virtualization R
>
> Tel.: +420 532 294 605
> Email: dc...@redhat.com
> IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> Web: www.redhat.com
> RHT Global #: 82-62605
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [vdsm] Running VDSM unit tests on Travis CI using Docker

[Nir Soffer]

On Wed, Apr 6, 2016 at 2:55 PM, Edward Haas  wrote:
>
>
> On Wed, Apr 6, 2016 at 2:41 PM, Nir Soffer  wrote:
>>
>> On Wed, Apr 6, 2016 at 2:33 PM, Edward Haas  wrote:
>> >
>> >
>> > On Wed, Apr 6, 2016 at 2:23 PM, Nir Soffer  wrote:
>> >>
>> >> On Wed, Apr 6, 2016 at 2:19 PM, Edward Haas  wrote:
>> >> >
>> >> >
>> >> > On Wed, Apr 6, 2016 at 1:41 PM, Milan Zamazal 
>> >> > wrote:
>> >> >>
>> >> >> Edward Haas  writes:
>> >> >>
>> >> >> > On Wed, Apr 6, 2016 at 11:39 AM, Milan Zamazal
>> >> >> > 
>> >> >> > wrote:
>> >> >> >
>> >> >> > Thank you, Edward, this is useful not only for CI. I use
>> >> >> > docker
>> >> >> > for
>> >> >> > building Vdsm and running its unit tests and this helped me to
>> >> >> > get
>> >> >> > the
>> >> >> > proper updated set of packages after recent changes in Vdsm.
>> >> >> >
>> >> >> > BTW, it seems that the following packages should be
>> >> >> > additionally
>> >> >> > added
>> >> >> > for `make check-all': psmisc, which, python-ioprocess
>> >> >> >
>> >> >> >
>> >> >> > Are you saying that make check is passing on your local machine?
>> >> >>
>> >> >> When I add the packages given above, `make check-all' (as well as
>> >> >> `make
>> >> >> check') works for me except for 4 tests in lib/vdsm/schedule.py that
>> >> >> produce the following errors with `make check-all':
>> >> >>
>> >> >> File "/home/pdm/ovirt/vdsm/vdsm-test/lib/vdsm/schedule.py", line
>> >> >> 134,
>> >> >> in schedule
>> >> >>   heapq.heappush(self._calls, (deadline, call))
>> >> >>   nose.proxy.TypeError: unorderable types: ScheduledCall() <
>> >> >> ScheduledCall()
>> >> >>
>> >> >> File "/home/pdm/ovirt/vdsm/vdsm-test/tests/scheduleTests.py",
>> >> >> line
>> >> >> 160, in test_latency
>> >> >>   med = ticker.latency[len(ticker.latency) / 2]
>> >> >>   nose.proxy.TypeError: list indices must be integers, not float
>> >> >>
>> >> >> Those are probably Python 3 failures that should be fixed in Vdsm.
>> >> >> The docker environment works fine for running the unit tests on my
>> >> >> machine.
>> >> >
>> >> >
>> >> > I ran it on Travis CI with your recommended addition, and I am
>> >> > getting
>> >> > this
>> >> > result: FAILED (SKIP=107, errors=14):
>> >> > You can view the run here:
>> >> > https://travis-ci.org/EdDev/vdsm/builds/121117253
>> >>
>> >> Sure, make check in master run tests that should not run on travis.
>> >>
>> >> Try the travis branch - after adding ioprocess to the docker image,
>> >> all tests should pass:
>> >> https://gerrit.ovirt.org/55738
>> >>
>> >> Nir
>> >
>> >
>> > Ok, will check it as well.
>> > But its a bit of a lie, many tests are skipped instead of not ran at
>> > all,
>> > this needs to be fixed.
>> > In addition, I find many tests as not unit tests, all tests should pass
>> > in a
>> > few seconds not in 2 minutes.
>>
>> Storage people always lie :-)
>>
>> We have @slowtest for marking slow tests. Unfortunately, some tests are
>> slow, and there is no value in mocking the thing you want to test.
>>
>> Nir
>
>
> Well, I will like to run only the unit tests, and you seem to try and merge
> the integration tests
> in the same run.

make check run only unit tests, I'm using NOSE_EVAL_ATTR to filter out the
integration tests:
https://gerrit.ovirt.org/#/c/55728/2/tests/run_tests_local.sh.in

Some integration tests are not marked yet, we will do this later.

>I think they need to be separated.
> I would like to see the unit tests pass in a few seconds, have no surprising
> skips and
> have no dependency or other services.

I agree all goals, but it will take more time.

We should follow the general rule:
http://c2.com/cgi/wiki?MakeItWorkMakeItRightMakeItFast

Nir
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] python-mock

[Rafael Martins]

- Original Message -
> From: "Barak Korren" 
> To: "Rafael Martins" 
> Cc: "shlomi ben david" , "devel" 
> 
> Sent: Wednesday, April 6, 2016 2:42:50 PM
> Subject: Re: [ovirt-devel] python-mock
> 
> >
> > We use mock for ovirt-setup-lib unit tests, and while they are not running
> > in Jenkins yet, we will activate a job for it soon.
> >
> 
> If the job is non-existent, you will most probably creates a
> standard-CI jobs that can get its own dependencies when it needs them,
> so this question is not relevant for you.

Sure, that's ok then.

Thanks.

Rafael

> --
> Barak Korren
> bkor...@redhat.com
> RHEV-CI Team
> 
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] python-mock

[Rafael Martins]

- Original Message -
> From: "Eyal Edri" 
> To: "Rafael Martins" 
> Cc: "shlomi ben david" , "devel" 
> 
> Sent: Wednesday, April 6, 2016 2:41:05 PM
> Subject: Re: [ovirt-devel] python-mock
> 
> On Wed, Apr 6, 2016 at 3:35 PM, Rafael Martins  wrote:
> 
> > - Original Message -
> > > From: "Shlomi Ben David" 
> > > To: devel@ovirt.org
> > > Sent: Wednesday, April 6, 2016 1:40:54 PM
> > > Subject: [ovirt-devel] python-mock
> > >
> > > Hi,
> > >
> > > I wanted to ask you if you know about a Jenkins job that is using
> > > 'python-mock' pkg? if you do please let me know.
> >
> > We use mock for ovirt-setup-lib unit tests, and while they are not running
> > in Jenkins yet, we will activate a job for it soon.
> >
> 
> AFAIK ovirt-setup-lib jobs uses standard CI, and you will get the pkg from
> mock (not python-mock :), so its not needed to the slave itself.

Sorry, I meant that we use python-mock. I always forget that we have a name 
clash here with the mock building tool. :)

The current ovirt-setup-lib jobs are not running the unit test suite. I started 
writing it some time ago, but hadn't time to finish testing everything and 
integrate it properly with jenkins yet, so it does not uses python-mock now, 
but will use soon.

Also, we have plans to add unit tests to more and more ovirt-setup packages, 
and they will use python-mock for sure.

Thanks.

Rafael

> 
> >
> > Thanks,
> >
> > Rafael
> >
> > > Thanks in advanced,
> > >
> > > --
> > > Shlomi Ben-David | Software Engineer | Red Hat ISRAEL
> > >
> > > OPEN SOURCE - 1 4 011 && 011 4 1
> > >
> > > ___
> > > Devel mailing list
> > > Devel@ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/devel
> > >
> > ___
> > Devel mailing list
> > Devel@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
> >
> >
> >
> 
> 
> --
> Eyal Edri
> Associate Manager
> RHEV DevOps
> EMEA ENG Virtualization R
> Red Hat Israel
> 
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
> 
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] python-mock

[Barak Korren]

>
> We use mock for ovirt-setup-lib unit tests, and while they are not running in 
> Jenkins yet, we will activate a job for it soon.
>

If the job is non-existent, you will most probably creates a
standard-CI jobs that can get its own dependencies when it needs them,
so this question is not relevant for you.

-- 
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] python-mock

[Eyal Edri]

On Wed, Apr 6, 2016 at 3:35 PM, Rafael Martins  wrote:

> - Original Message -
> > From: "Shlomi Ben David" 
> > To: devel@ovirt.org
> > Sent: Wednesday, April 6, 2016 1:40:54 PM
> > Subject: [ovirt-devel] python-mock
> >
> > Hi,
> >
> > I wanted to ask you if you know about a Jenkins job that is using
> > 'python-mock' pkg? if you do please let me know.
>
> We use mock for ovirt-setup-lib unit tests, and while they are not running
> in Jenkins yet, we will activate a job for it soon.
>

AFAIK ovirt-setup-lib jobs uses standard CI, and you will get the pkg from
mock (not python-mock :), so its not needed to the slave itself.


>
> Thanks,
>
> Rafael
>
> > Thanks in advanced,
> >
> > --
> > Shlomi Ben-David | Software Engineer | Red Hat ISRAEL
> >
> > OPEN SOURCE - 1 4 011 && 011 4 1
> >
> > ___
> > Devel mailing list
> > Devel@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
> >
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
>
>


-- 
Eyal Edri
Associate Manager
RHEV DevOps
EMEA ENG Virtualization R
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] python-mock

[Rafael Martins]

- Original Message -
> From: "Shlomi Ben David" 
> To: devel@ovirt.org
> Sent: Wednesday, April 6, 2016 1:40:54 PM
> Subject: [ovirt-devel] python-mock
> 
> Hi,
> 
> I wanted to ask you if you know about a Jenkins job that is using
> 'python-mock' pkg? if you do please let me know.

We use mock for ovirt-setup-lib unit tests, and while they are not running in 
Jenkins yet, we will activate a job for it soon.

Thanks,

Rafael

> Thanks in advanced,
> 
> --
> Shlomi Ben-David | Software Engineer | Red Hat ISRAEL
> 
> OPEN SOURCE - 1 4 011 && 011 4 1
> 
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
> 
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] python-mock

[Eyal Edri]

My only guess would be old VDSM functional tests or unit test using mock.
Yaniv/Danken?

e.

On Wed, Apr 6, 2016 at 2:40 PM, Shlomi Ben David 
wrote:

> Hi,
>
> I wanted to ask you if you know about a Jenkins job that is using
> 'python-mock' pkg? if you do please let me know.
>
> Thanks in advanced,
>
> --
> Shlomi Ben-David | Software Engineer | Red Hat ISRAEL
>
> OPEN SOURCE - 1 4 011 && 011 4 1
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
>
>


-- 
Eyal Edri
Associate Manager
RHEV DevOps
EMEA ENG Virtualization R
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [vdsm] Running VDSM unit tests on Travis CI using Docker

[Edward Haas]

On Wed, Apr 6, 2016 at 2:41 PM, Nir Soffer  wrote:

> On Wed, Apr 6, 2016 at 2:33 PM, Edward Haas  wrote:
> >
> >
> > On Wed, Apr 6, 2016 at 2:23 PM, Nir Soffer  wrote:
> >>
> >> On Wed, Apr 6, 2016 at 2:19 PM, Edward Haas  wrote:
> >> >
> >> >
> >> > On Wed, Apr 6, 2016 at 1:41 PM, Milan Zamazal 
> >> > wrote:
> >> >>
> >> >> Edward Haas  writes:
> >> >>
> >> >> > On Wed, Apr 6, 2016 at 11:39 AM, Milan Zamazal <
> mzama...@redhat.com>
> >> >> > wrote:
> >> >> >
> >> >> > Thank you, Edward, this is useful not only for CI. I use docker
> >> >> > for
> >> >> > building Vdsm and running its unit tests and this helped me to
> >> >> > get
> >> >> > the
> >> >> > proper updated set of packages after recent changes in Vdsm.
> >> >> >
> >> >> > BTW, it seems that the following packages should be
> additionally
> >> >> > added
> >> >> > for `make check-all': psmisc, which, python-ioprocess
> >> >> >
> >> >> >
> >> >> > Are you saying that make check is passing on your local machine?
> >> >>
> >> >> When I add the packages given above, `make check-all' (as well as
> `make
> >> >> check') works for me except for 4 tests in lib/vdsm/schedule.py that
> >> >> produce the following errors with `make check-all':
> >> >>
> >> >> File "/home/pdm/ovirt/vdsm/vdsm-test/lib/vdsm/schedule.py", line
> >> >> 134,
> >> >> in schedule
> >> >>   heapq.heappush(self._calls, (deadline, call))
> >> >>   nose.proxy.TypeError: unorderable types: ScheduledCall() <
> >> >> ScheduledCall()
> >> >>
> >> >> File "/home/pdm/ovirt/vdsm/vdsm-test/tests/scheduleTests.py",
> line
> >> >> 160, in test_latency
> >> >>   med = ticker.latency[len(ticker.latency) / 2]
> >> >>   nose.proxy.TypeError: list indices must be integers, not float
> >> >>
> >> >> Those are probably Python 3 failures that should be fixed in Vdsm.
> >> >> The docker environment works fine for running the unit tests on my
> >> >> machine.
> >> >
> >> >
> >> > I ran it on Travis CI with your recommended addition, and I am getting
> >> > this
> >> > result: FAILED (SKIP=107, errors=14):
> >> > You can view the run here:
> >> > https://travis-ci.org/EdDev/vdsm/builds/121117253
> >>
> >> Sure, make check in master run tests that should not run on travis.
> >>
> >> Try the travis branch - after adding ioprocess to the docker image,
> >> all tests should pass:
> >> https://gerrit.ovirt.org/55738
> >>
> >> Nir
> >
> >
> > Ok, will check it as well.
> > But its a bit of a lie, many tests are skipped instead of not ran at all,
> > this needs to be fixed.
> > In addition, I find many tests as not unit tests, all tests should pass
> in a
> > few seconds not in 2 minutes.
>
> Storage people always lie :-)
>
> We have @slowtest for marking slow tests. Unfortunately, some tests are
> slow, and there is no value in mocking the thing you want to test.
>
> Nir
>

Well, I will like to run only the unit tests, and you seem to try and merge
the integration tests
in the same run. I think they need to be separated.
I would like to see the unit tests pass in a few seconds, have no
surprising skips and
have no dependency or other services.
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [vdsm] Running VDSM unit tests on Travis CI using Docker

[Nir Soffer]

On Wed, Apr 6, 2016 at 2:33 PM, Edward Haas  wrote:
>
>
> On Wed, Apr 6, 2016 at 2:23 PM, Nir Soffer  wrote:
>>
>> On Wed, Apr 6, 2016 at 2:19 PM, Edward Haas  wrote:
>> >
>> >
>> > On Wed, Apr 6, 2016 at 1:41 PM, Milan Zamazal 
>> > wrote:
>> >>
>> >> Edward Haas  writes:
>> >>
>> >> > On Wed, Apr 6, 2016 at 11:39 AM, Milan Zamazal 
>> >> > wrote:
>> >> >
>> >> > Thank you, Edward, this is useful not only for CI. I use docker
>> >> > for
>> >> > building Vdsm and running its unit tests and this helped me to
>> >> > get
>> >> > the
>> >> > proper updated set of packages after recent changes in Vdsm.
>> >> >
>> >> > BTW, it seems that the following packages should be additionally
>> >> > added
>> >> > for `make check-all': psmisc, which, python-ioprocess
>> >> >
>> >> >
>> >> > Are you saying that make check is passing on your local machine?
>> >>
>> >> When I add the packages given above, `make check-all' (as well as `make
>> >> check') works for me except for 4 tests in lib/vdsm/schedule.py that
>> >> produce the following errors with `make check-all':
>> >>
>> >> File "/home/pdm/ovirt/vdsm/vdsm-test/lib/vdsm/schedule.py", line
>> >> 134,
>> >> in schedule
>> >>   heapq.heappush(self._calls, (deadline, call))
>> >>   nose.proxy.TypeError: unorderable types: ScheduledCall() <
>> >> ScheduledCall()
>> >>
>> >> File "/home/pdm/ovirt/vdsm/vdsm-test/tests/scheduleTests.py", line
>> >> 160, in test_latency
>> >>   med = ticker.latency[len(ticker.latency) / 2]
>> >>   nose.proxy.TypeError: list indices must be integers, not float
>> >>
>> >> Those are probably Python 3 failures that should be fixed in Vdsm.
>> >> The docker environment works fine for running the unit tests on my
>> >> machine.
>> >
>> >
>> > I ran it on Travis CI with your recommended addition, and I am getting
>> > this
>> > result: FAILED (SKIP=107, errors=14):
>> > You can view the run here:
>> > https://travis-ci.org/EdDev/vdsm/builds/121117253
>>
>> Sure, make check in master run tests that should not run on travis.
>>
>> Try the travis branch - after adding ioprocess to the docker image,
>> all tests should pass:
>> https://gerrit.ovirt.org/55738
>>
>> Nir
>
>
> Ok, will check it as well.
> But its a bit of a lie, many tests are skipped instead of not ran at all,
> this needs to be fixed.
> In addition, I find many tests as not unit tests, all tests should pass in a
> few seconds not in 2 minutes.

Storage people always lie :-)

We have @slowtest for marking slow tests. Unfortunately, some tests are
slow, and there is no value in mocking the thing you want to test.

Nir
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] python-mock

[Shlomi Ben David]

Hi,

I wanted to ask you if you know about a Jenkins job that is using
'python-mock' pkg? if you do please let me know.

Thanks in advanced,

-- 
Shlomi Ben-David | Software Engineer | Red Hat ISRAEL

OPEN SOURCE - 1 4 011 && 011 4 1

___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [vdsm] Running VDSM unit tests on Travis CI using Docker

[Edward Haas]

On Wed, Apr 6, 2016 at 2:23 PM, Nir Soffer  wrote:

> On Wed, Apr 6, 2016 at 2:19 PM, Edward Haas  wrote:
> >
> >
> > On Wed, Apr 6, 2016 at 1:41 PM, Milan Zamazal 
> wrote:
> >>
> >> Edward Haas  writes:
> >>
> >> > On Wed, Apr 6, 2016 at 11:39 AM, Milan Zamazal 
> >> > wrote:
> >> >
> >> > Thank you, Edward, this is useful not only for CI. I use docker
> for
> >> > building Vdsm and running its unit tests and this helped me to get
> >> > the
> >> > proper updated set of packages after recent changes in Vdsm.
> >> >
> >> > BTW, it seems that the following packages should be additionally
> >> > added
> >> > for `make check-all': psmisc, which, python-ioprocess
> >> >
> >> >
> >> > Are you saying that make check is passing on your local machine?
> >>
> >> When I add the packages given above, `make check-all' (as well as `make
> >> check') works for me except for 4 tests in lib/vdsm/schedule.py that
> >> produce the following errors with `make check-all':
> >>
> >> File "/home/pdm/ovirt/vdsm/vdsm-test/lib/vdsm/schedule.py", line
> 134,
> >> in schedule
> >>   heapq.heappush(self._calls, (deadline, call))
> >>   nose.proxy.TypeError: unorderable types: ScheduledCall() <
> >> ScheduledCall()
> >>
> >> File "/home/pdm/ovirt/vdsm/vdsm-test/tests/scheduleTests.py", line
> >> 160, in test_latency
> >>   med = ticker.latency[len(ticker.latency) / 2]
> >>   nose.proxy.TypeError: list indices must be integers, not float
> >>
> >> Those are probably Python 3 failures that should be fixed in Vdsm.
> >> The docker environment works fine for running the unit tests on my
> >> machine.
> >
> >
> > I ran it on Travis CI with your recommended addition, and I am getting
> this
> > result: FAILED (SKIP=107, errors=14):
> > You can view the run here:
> https://travis-ci.org/EdDev/vdsm/builds/121117253
>
> Sure, make check in master run tests that should not run on travis.
>
> Try the travis branch - after adding ioprocess to the docker image,
> all tests should pass:
> https://gerrit.ovirt.org/55738
>
> Nir
>

Ok, will check it as well.
But its a bit of a lie, many tests are skipped instead of not ran at all,
this needs to be fixed.
In addition, I find many tests as not unit tests, all tests should pass in
a few seconds not in 2 minutes.
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [vdsm] Running VDSM unit tests on Travis CI using Docker

[David Caro]

On 04/06 14:31, Yaniv Kaul wrote:
> On Wed, Apr 6, 2016 at 2:23 PM, David Caro  wrote:
> 
> > On 04/06 14:19, Edward Haas wrote:
> > > On Wed, Apr 6, 2016 at 1:41 PM, Milan Zamazal 
> > wrote:
> > >
> > > > Edward Haas  writes:
> > > >
> > > > > On Wed, Apr 6, 2016 at 11:39 AM, Milan Zamazal 
> > > > wrote:
> > > > >
> > > > > Thank you, Edward, this is useful not only for CI. I use docker
> > for
> > > > > building Vdsm and running its unit tests and this helped me to
> > get
> > > > the
> > > > > proper updated set of packages after recent changes in Vdsm.
> > > > >
> > > > > BTW, it seems that the following packages should be additionally
> > > > added
> > > > > for `make check-all': psmisc, which, python-ioprocess
> > > > >
> > > > >
> > > > > Are you saying that make check is passing on your local machine?
> > > >
> > > > When I add the packages given above, `make check-all' (as well as `make
> > > > check') works for me except for 4 tests in lib/vdsm/schedule.py that
> > > > produce the following errors with `make check-all':
> > > >
> > > > File "/home/pdm/ovirt/vdsm/vdsm-test/lib/vdsm/schedule.py", line
> > 134,
> > > > in schedule
> > > >   heapq.heappush(self._calls, (deadline, call))
> > > >   nose.proxy.TypeError: unorderable types: ScheduledCall() <
> > > > ScheduledCall()
> > > >
> > > > File "/home/pdm/ovirt/vdsm/vdsm-test/tests/scheduleTests.py", line
> > > > 160, in test_latency
> > > >   med = ticker.latency[len(ticker.latency) / 2]
> > > >   nose.proxy.TypeError: list indices must be integers, not float
> > > >
> > > > Those are probably Python 3 failures that should be fixed in Vdsm.
> > > > The docker environment works fine for running the unit tests on my
> > > > machine.
> > > >
> > >
> > > I ran it on Travis CI with your recommended addition, and I am getting
> > this
> > > result: FAILED (SKIP=107, errors=14):
> > > You can view the run here:
> > https://travis-ci.org/EdDev/vdsm/builds/121117253
> >
> >
> > Afaik, you won't be able to run any tests that touch networking, or kernel
> > modules (bonding and such). That is as much a limitation of travis as of
> > docker, that was one of the points why we started using chroots instead of
> > docker containers on ovirt ci.
> >
> 
> All of those should run fine in Lago, right?

Yep, they run ok on chroot (with some mount magic) and they should run without
any magic on lago

> Y.
> 
> 
> >
> >
> > > ___
> > > Devel mailing list
> > > Devel@ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/devel
> >
> >
> > --
> > David Caro
> >
> > Red Hat S.L.
> > Continuous Integration Engineer - EMEA ENG Virtualization R
> >
> > Tel.: +420 532 294 605
> > Email: dc...@redhat.com
> > IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> > Web: www.redhat.com
> > RHT Global #: 82-62605
> >
> > ___
> > Devel mailing list
> > Devel@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
> >

> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel


-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R

Tel.: +420 532 294 605
Email: dc...@redhat.com
IRC: dcaro|dcaroest@{freenode|oftc|redhat}
Web: www.redhat.com
RHT Global #: 82-62605


signature.asc
Description: PGP signature
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [vdsm] Running VDSM unit tests on Travis CI using Docker

[Yaniv Kaul]

On Wed, Apr 6, 2016 at 2:23 PM, David Caro  wrote:

> On 04/06 14:19, Edward Haas wrote:
> > On Wed, Apr 6, 2016 at 1:41 PM, Milan Zamazal 
> wrote:
> >
> > > Edward Haas  writes:
> > >
> > > > On Wed, Apr 6, 2016 at 11:39 AM, Milan Zamazal 
> > > wrote:
> > > >
> > > > Thank you, Edward, this is useful not only for CI. I use docker
> for
> > > > building Vdsm and running its unit tests and this helped me to
> get
> > > the
> > > > proper updated set of packages after recent changes in Vdsm.
> > > >
> > > > BTW, it seems that the following packages should be additionally
> > > added
> > > > for `make check-all': psmisc, which, python-ioprocess
> > > >
> > > >
> > > > Are you saying that make check is passing on your local machine?
> > >
> > > When I add the packages given above, `make check-all' (as well as `make
> > > check') works for me except for 4 tests in lib/vdsm/schedule.py that
> > > produce the following errors with `make check-all':
> > >
> > > File "/home/pdm/ovirt/vdsm/vdsm-test/lib/vdsm/schedule.py", line
> 134,
> > > in schedule
> > >   heapq.heappush(self._calls, (deadline, call))
> > >   nose.proxy.TypeError: unorderable types: ScheduledCall() <
> > > ScheduledCall()
> > >
> > > File "/home/pdm/ovirt/vdsm/vdsm-test/tests/scheduleTests.py", line
> > > 160, in test_latency
> > >   med = ticker.latency[len(ticker.latency) / 2]
> > >   nose.proxy.TypeError: list indices must be integers, not float
> > >
> > > Those are probably Python 3 failures that should be fixed in Vdsm.
> > > The docker environment works fine for running the unit tests on my
> > > machine.
> > >
> >
> > I ran it on Travis CI with your recommended addition, and I am getting
> this
> > result: FAILED (SKIP=107, errors=14):
> > You can view the run here:
> https://travis-ci.org/EdDev/vdsm/builds/121117253
>
>
> Afaik, you won't be able to run any tests that touch networking, or kernel
> modules (bonding and such). That is as much a limitation of travis as of
> docker, that was one of the points why we started using chroots instead of
> docker containers on ovirt ci.
>

All of those should run fine in Lago, right?
Y.


>
>
> > ___
> > Devel mailing list
> > Devel@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
>
>
> --
> David Caro
>
> Red Hat S.L.
> Continuous Integration Engineer - EMEA ENG Virtualization R
>
> Tel.: +420 532 294 605
> Email: dc...@redhat.com
> IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> Web: www.redhat.com
> RHT Global #: 82-62605
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [vdsm] Running VDSM unit tests on Travis CI using Docker

[Milan Zamazal]

Edward Haas  writes:

> I ran it on Travis CI with your recommended addition, and I am getting this
> result: FAILED (SKIP=107, errors=14): 
> You can view the run here: https://travis-ci.org/EdDev/vdsm/builds/121117253

I see, the difference is I don't run the tests as root in my docker.
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [vdsm] Running VDSM unit tests on Travis CI using Docker

[Edward Haas]

On Wed, Apr 6, 2016 at 2:23 PM, David Caro  wrote:

> On 04/06 14:19, Edward Haas wrote:
> > On Wed, Apr 6, 2016 at 1:41 PM, Milan Zamazal 
> wrote:
> >
> > > Edward Haas  writes:
> > >
> > > > On Wed, Apr 6, 2016 at 11:39 AM, Milan Zamazal 
> > > wrote:
> > > >
> > > > Thank you, Edward, this is useful not only for CI. I use docker
> for
> > > > building Vdsm and running its unit tests and this helped me to
> get
> > > the
> > > > proper updated set of packages after recent changes in Vdsm.
> > > >
> > > > BTW, it seems that the following packages should be additionally
> > > added
> > > > for `make check-all': psmisc, which, python-ioprocess
> > > >
> > > >
> > > > Are you saying that make check is passing on your local machine?
> > >
> > > When I add the packages given above, `make check-all' (as well as `make
> > > check') works for me except for 4 tests in lib/vdsm/schedule.py that
> > > produce the following errors with `make check-all':
> > >
> > > File "/home/pdm/ovirt/vdsm/vdsm-test/lib/vdsm/schedule.py", line
> 134,
> > > in schedule
> > >   heapq.heappush(self._calls, (deadline, call))
> > >   nose.proxy.TypeError: unorderable types: ScheduledCall() <
> > > ScheduledCall()
> > >
> > > File "/home/pdm/ovirt/vdsm/vdsm-test/tests/scheduleTests.py", line
> > > 160, in test_latency
> > >   med = ticker.latency[len(ticker.latency) / 2]
> > >   nose.proxy.TypeError: list indices must be integers, not float
> > >
> > > Those are probably Python 3 failures that should be fixed in Vdsm.
> > > The docker environment works fine for running the unit tests on my
> > > machine.
> > >
> >
> > I ran it on Travis CI with your recommended addition, and I am getting
> this
> > result: FAILED (SKIP=107, errors=14):
> > You can view the run here:
> https://travis-ci.org/EdDev/vdsm/builds/121117253
>
>
> Afaik, you won't be able to run any tests that touch networking, or kernel
> modules (bonding and such). That is as much a limitation of travis as of
> docker, that was one of the points why we started using chroots instead of
> docker containers on ovirt ci.
>

Yes, that is why I intended it for unit tests only, not for integration or
functional.
We may find some integration tests that do pass, that needs some more
investigation, but it's out of my original intent
.

>
>
> > ___
> > Devel mailing list
> > Devel@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
>
>
> --
> David Caro
>
> Red Hat S.L.
> Continuous Integration Engineer - EMEA ENG Virtualization R
>
> Tel.: +420 532 294 605
> Email: dc...@redhat.com
> IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> Web: www.redhat.com
> RHT Global #: 82-62605
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [vdsm] Running VDSM unit tests on Travis CI using Docker

[David Caro]

On 04/06 14:19, Edward Haas wrote:
> On Wed, Apr 6, 2016 at 1:41 PM, Milan Zamazal  wrote:
> 
> > Edward Haas  writes:
> >
> > > On Wed, Apr 6, 2016 at 11:39 AM, Milan Zamazal 
> > wrote:
> > >
> > > Thank you, Edward, this is useful not only for CI. I use docker for
> > > building Vdsm and running its unit tests and this helped me to get
> > the
> > > proper updated set of packages after recent changes in Vdsm.
> > >
> > > BTW, it seems that the following packages should be additionally
> > added
> > > for `make check-all': psmisc, which, python-ioprocess
> > >
> > >
> > > Are you saying that make check is passing on your local machine?
> >
> > When I add the packages given above, `make check-all' (as well as `make
> > check') works for me except for 4 tests in lib/vdsm/schedule.py that
> > produce the following errors with `make check-all':
> >
> > File "/home/pdm/ovirt/vdsm/vdsm-test/lib/vdsm/schedule.py", line 134,
> > in schedule
> >   heapq.heappush(self._calls, (deadline, call))
> >   nose.proxy.TypeError: unorderable types: ScheduledCall() <
> > ScheduledCall()
> >
> > File "/home/pdm/ovirt/vdsm/vdsm-test/tests/scheduleTests.py", line
> > 160, in test_latency
> >   med = ticker.latency[len(ticker.latency) / 2]
> >   nose.proxy.TypeError: list indices must be integers, not float
> >
> > Those are probably Python 3 failures that should be fixed in Vdsm.
> > The docker environment works fine for running the unit tests on my
> > machine.
> >
> 
> I ran it on Travis CI with your recommended addition, and I am getting this
> result: FAILED (SKIP=107, errors=14):
> You can view the run here: https://travis-ci.org/EdDev/vdsm/builds/121117253


Afaik, you won't be able to run any tests that touch networking, or kernel
modules (bonding and such). That is as much a limitation of travis as of
docker, that was one of the points why we started using chroots instead of
docker containers on ovirt ci.


> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel


-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R

Tel.: +420 532 294 605
Email: dc...@redhat.com
IRC: dcaro|dcaroest@{freenode|oftc|redhat}
Web: www.redhat.com
RHT Global #: 82-62605


signature.asc
Description: PGP signature
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [vdsm] Running VDSM unit tests on Travis CI using Docker

[Nir Soffer]

On Wed, Apr 6, 2016 at 2:19 PM, Edward Haas  wrote:
>
>
> On Wed, Apr 6, 2016 at 1:41 PM, Milan Zamazal  wrote:
>>
>> Edward Haas  writes:
>>
>> > On Wed, Apr 6, 2016 at 11:39 AM, Milan Zamazal 
>> > wrote:
>> >
>> > Thank you, Edward, this is useful not only for CI. I use docker for
>> > building Vdsm and running its unit tests and this helped me to get
>> > the
>> > proper updated set of packages after recent changes in Vdsm.
>> >
>> > BTW, it seems that the following packages should be additionally
>> > added
>> > for `make check-all': psmisc, which, python-ioprocess
>> >
>> >
>> > Are you saying that make check is passing on your local machine?
>>
>> When I add the packages given above, `make check-all' (as well as `make
>> check') works for me except for 4 tests in lib/vdsm/schedule.py that
>> produce the following errors with `make check-all':
>>
>> File "/home/pdm/ovirt/vdsm/vdsm-test/lib/vdsm/schedule.py", line 134,
>> in schedule
>>   heapq.heappush(self._calls, (deadline, call))
>>   nose.proxy.TypeError: unorderable types: ScheduledCall() <
>> ScheduledCall()
>>
>> File "/home/pdm/ovirt/vdsm/vdsm-test/tests/scheduleTests.py", line
>> 160, in test_latency
>>   med = ticker.latency[len(ticker.latency) / 2]
>>   nose.proxy.TypeError: list indices must be integers, not float
>>
>> Those are probably Python 3 failures that should be fixed in Vdsm.
>> The docker environment works fine for running the unit tests on my
>> machine.
>
>
> I ran it on Travis CI with your recommended addition, and I am getting this
> result: FAILED (SKIP=107, errors=14):
> You can view the run here: https://travis-ci.org/EdDev/vdsm/builds/121117253

Sure, make check in master run tests that should not run on travis.

Try the travis branch - after adding ioprocess to the docker image,
all tests should pass:
https://gerrit.ovirt.org/55738

Nir
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [vdsm] Running VDSM unit tests on Travis CI using Docker

[Edward Haas]

On Wed, Apr 6, 2016 at 1:41 PM, Milan Zamazal  wrote:

> Edward Haas  writes:
>
> > On Wed, Apr 6, 2016 at 11:39 AM, Milan Zamazal 
> wrote:
> >
> > Thank you, Edward, this is useful not only for CI. I use docker for
> > building Vdsm and running its unit tests and this helped me to get
> the
> > proper updated set of packages after recent changes in Vdsm.
> >
> > BTW, it seems that the following packages should be additionally
> added
> > for `make check-all': psmisc, which, python-ioprocess
> >
> >
> > Are you saying that make check is passing on your local machine?
>
> When I add the packages given above, `make check-all' (as well as `make
> check') works for me except for 4 tests in lib/vdsm/schedule.py that
> produce the following errors with `make check-all':
>
> File "/home/pdm/ovirt/vdsm/vdsm-test/lib/vdsm/schedule.py", line 134,
> in schedule
>   heapq.heappush(self._calls, (deadline, call))
>   nose.proxy.TypeError: unorderable types: ScheduledCall() <
> ScheduledCall()
>
> File "/home/pdm/ovirt/vdsm/vdsm-test/tests/scheduleTests.py", line
> 160, in test_latency
>   med = ticker.latency[len(ticker.latency) / 2]
>   nose.proxy.TypeError: list indices must be integers, not float
>
> Those are probably Python 3 failures that should be fixed in Vdsm.
> The docker environment works fine for running the unit tests on my
> machine.
>

I ran it on Travis CI with your recommended addition, and I am getting this
result: FAILED (SKIP=107, errors=14):
You can view the run here: https://travis-ci.org/EdDev/vdsm/builds/121117253
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [vdsm] Running VDSM unit tests on Travis CI using Docker

[Milan Zamazal]

Nir Soffer  writes:

> Can you send a patch to add the missing packages to our travis config?

I think it's better to continue on your `travis' topic:

- `psmisc' is needed by tests/fuserTests.py (it contains /usr/sbin/fuser)

- `which' is needed by CommandPathTests.testExistingNotInPaths in 
tests/utilsTests.py"
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [vdsm] Running VDSM unit tests on Travis CI using Docker

[Nir Soffer]

On Tue, Apr 5, 2016 at 6:22 PM, Edward Haas  wrote:
> Hi All,
>
> The following patch is proposing to run VDSM unit tests on Travis CI.
> It uses Docker, GitHub and Travis CI integration.
>
> We can extend the usage and run coverage with historic information using
> coveralls.io service (or similar).
>
> https://gerrit.ovirt.org/#/c/54856
>
> Results of the run can be seen here: https://travis-ci.org/EdDev/vdsm

Thanks for this great work!

With little more work[1], we can run now the entire test suite on travis [2]!

Nir

[1] 
https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:travis
[2] https://travis-ci.org/nirs/vdsm/builds/121115473
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] [ANN] oVirt 4.0.0 First Alpha Release is now available for testing

[Sandro Bonazzola]

The oVirt Project is pleased to announce the availability of the First
Alpha Release of oVirt 4.0.0 for testing, as of April 5th, 2016

This is pre-release software. Please take a look at our community page[1]
to know how to ask questions and interact with developers and users.
All issues or bugs should be reported via oVirt Bugzilla[2].
This pre-release should not to be used in production, and it is not feature
complete

This release is available now for:
* Fedora 23
* Red Hat Enterprise Linux 7.2 or later
* CentOS Linux (or similar) 7.2 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.2 or later
* CentOS Linux (or similar) 7.2 or later
* Fedora 23
* oVirt Next Generation Node 4.0

See the release notes draft [3] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
* A new oVirt Live ISO is already available [4].
* A new oVirt Next Generation Node is already available[4]
* A new oVirt Engine Appliance is already available
* Mirrors[5] might need up to one day to synchronize.

Additional Resources:
* Read more about the oVirt 4.0.0 alpha release highlights:
http://www.ovirt.org/release/4.0.0/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] https://www.ovirt.org/community/
[2]  https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
[3] http://www.ovirt.org/release/4.0.0/
[4] http://resources.ovirt.org/pub/ovirt-4.0_alpha1/iso/
[5] http://www.ovirt.org/Repository_mirrors#Current_mirrors

-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [vdsm] Running VDSM unit tests on Travis CI using Docker

[Milan Zamazal]

Edward Haas  writes:

> On Wed, Apr 6, 2016 at 11:39 AM, Milan Zamazal  wrote:
>
> Thank you, Edward, this is useful not only for CI. I use docker for
> building Vdsm and running its unit tests and this helped me to get the
> proper updated set of packages after recent changes in Vdsm.
> 
> BTW, it seems that the following packages should be additionally added
> for `make check-all': psmisc, which, python-ioprocess
> 
>
> Are you saying that make check is passing on your local machine?

When I add the packages given above, `make check-all' (as well as `make
check') works for me except for 4 tests in lib/vdsm/schedule.py that
produce the following errors with `make check-all':

File "/home/pdm/ovirt/vdsm/vdsm-test/lib/vdsm/schedule.py", line 134, in 
schedule
  heapq.heappush(self._calls, (deadline, call))
  nose.proxy.TypeError: unorderable types: ScheduledCall() < ScheduledCall()

File "/home/pdm/ovirt/vdsm/vdsm-test/tests/scheduleTests.py", line 160, in 
test_latency
  med = ticker.latency[len(ticker.latency) / 2]
  nose.proxy.TypeError: list indices must be integers, not float

Those are probably Python 3 failures that should be fixed in Vdsm.
The docker environment works fine for running the unit tests on my
machine.
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [vdsm] Running VDSM unit tests on Travis CI using Docker

[Edward Haas]

On Wed, Apr 6, 2016 at 11:39 AM, Milan Zamazal  wrote:

> Edward Haas  writes:
>
> > The following patch is proposing to run VDSM unit tests on Travis CI.
>
> Thank you, Edward, this is useful not only for CI.  I use docker for
> building Vdsm and running its unit tests and this helped me to get the
> proper updated set of packages after recent changes in Vdsm.
>
> BTW, it seems that the following packages should be additionally added
> for `make check-all': psmisc, which, python-ioprocess
>

Are you saying that make check is passing on your local machine?
On Travis CI I could not run the full test suite. Maybe I need to check
again.


> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] How to debug NullPointerException for project restapi-def inition of version 3.6.4.1?

[Juan Hernández]

On 04/06/2016 11:51 AM, Kai Kang wrote:
> Hi,
> 
> I am building ovirt-engine 3.6.4.1 and failed with NullPointerException.
> I build for cross compile with commands:
> 
> 
>
> tmp_repo=/buildarea3/kkang/builds/Mar31-ovrit-engine/bitbake_build/tmp/work/corei7-64-wrs-linux/ovirt-engine/3.6.4.1-r0/repo
> export MAVEN_OPTS="-Dmaven.repo.local=$tmp_repo"
> 
> makeEXTRA_BUILD_FLAGS="-s
> /buildarea3/kkang/builds/Mar31-ovrit-engine/bitbake_build/tmp/work/corei7-64-wrs-linux/ovirt-engine/3.6.4.1-r0/settings.xml
> --debug --offline"-j1 BUILD_GWT=1 BUILD_LOCALES=0
> BUILD_UT=1  BUILD_VALIDATION=0
>  JAVA_DIR=/usr/share/ovirt-engine/java   LOCALSTATE_DIR=/var
> MAVENPOM_DIR=/usr/share/ovirt-engine/maven-poms PREFIX=/usr
> SYSCONF_DIR=/etcPKG_SYSCONF_DIR=/etc/ovirt-engine  
> PKG_DOC_DIR=/usr/doc/ovirt-engine  
> PKG_EAR_DIR=/usr/share/ovirt-engine/engine.ear
>  PKG_PKI_DIR=/etc/pki/ovirt-engine  
> PKG_JBOSS_MODULES=/usr/share/ovirt-engine/modules  
> PKG_CACHE_DIR=/var/cache/ovirt-engine  
> PKG_LOG_DIR=/var/log/ovirt-engine  
> PKG_TMP_DIR=/var/tmp/ovirt-engine  
> PKG_STATE_DIR=/var/lib/ovirt-engine PKG_USER=ovirt  PKG_GROUP=ovirt
>  all
> 
> 
> The error messages show:
> 
> [INFO] oVirt Engine API Definition ... FAILURE [1.476s]
> ...
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:1.2:java (default) on project
> restapi-definition: An exception occured while executing the Java class.
> null: InvocationTargetException: NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal org.codehaus.mojo:exec-maven-plugin:1.2:java (default) on
> project restapi-definition: An exception occured while executing the
> Java class. null
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> ...
> at javax.xml.bind.JAXB.marshal(JAXB.java:332)
> at
> org.ovirt.engine.api.rsdl.RsdlManager.serializeRsdl(RsdlManager.java:134)
> at
> org.ovirt.engine.api.rsdl.RsdlManager.generateRsdlFile(RsdlManager.java:84)
> at org.ovirt.engine.api.rsdl.RsdlManager.main(RsdlManager.java:58)
> ... 6 more
> 
> 
> My questions are:
> 
> 1 I know the error occurs in
> file 
> backend/manager/modules/restapi/interface/definition/src/main/java/org/ovirt/engine/api/rsdl/RsdlManager.java,
> but how to debug it?
> 
> 2 When I remove pom and jar files of javax.xml.bind.JAXB in mave repo
> with offline mode, it still could find the class.
> Which javax.xml.bind.JAXB is used? I searched the ovirt engine repo but
> didn't find it either.
> 

The version of JAXB used by that area of the code is the version of JAXB
included in the JDK that you are using for the build. So the question is
what version of the JDK are you using?

-- 
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
3ºD, 28016 Madrid, Spain
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [vdsm] Running VDSM unit tests on Travis CI using Docker

[Milan Zamazal]

Edward Haas  writes:

> The following patch is proposing to run VDSM unit tests on Travis CI.

Thank you, Edward, this is useful not only for CI.  I use docker for
building Vdsm and running its unit tests and this helped me to get the
proper updated set of packages after recent changes in Vdsm.

BTW, it seems that the following packages should be additionally added
for `make check-all': psmisc, which, python-ioprocess
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [vdsm] Running VDSM unit tests on Travis CI using Docker

[Dan Kenigsberg]

On Tue, Apr 05, 2016 at 06:22:20PM +0300, Edward Haas wrote:
> Hi All,
> 
> The following patch is proposing to run VDSM unit tests on Travis CI.
> It uses Docker, GitHub and Travis CI integration.
> 
> We can extend the usage and run coverage with historic information using
> coveralls.io service (or similar).
> 
> https://gerrit.ovirt.org/#/c/54856
> 
> Results of the run can be seen here: https://travis-ci.org/EdDev/vdsm

Thanks Edy.

I've merged your patch to see how this historical data accumulate in
https://travis-ci.org/EdDev/vdsm/builds

If all is well for a week or so, I suggest that infra@ovirt adds vdsm
to https://travis-ci.org/ovirt and move your el7 docker image to
https://hub.docker.com/u/ovirt/ to make this thing more official.

Regards,
Dan.
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel