[ovirt-devel] Re: [VDSM] travis tests fail consistently since Apr 14

2018-06-11 Thread Nir Soffer 
On Mon, Jun 11, 2018 at 1:03 PM Maor Lipchuk  wrote:

> On Tue, Jun 5, 2018 at 9:40 AM, Dan Kenigsberg  wrote:
>
>> On Mon, Jun 4, 2018 at 7:14 PM, Nir Soffer  wrote:
>> > On Mon, Jun 4, 2018 at 6:56 PM Dan Kenigsberg 
>> wrote:
>> >>
>> >> On Tue, May 8, 2018 at 11:59 AM, Nir Soffer 
>> wrote:
>> >> > There are several issues:
>> >> >
>> >> > 1. coverage fail after this patch:
>> >> >
>> >> >
>> https://github.com/oVirt/vdsm/commit/6b905c2c134bcf344961d28eefbd05f2838d2ec8
>> >> >
>> >> > https://travis-ci.org/oVirt/vdsm/builds/366574414
>> >> > ...
>> >> > pwd
>> >> > /vdsm/tests
>> >> > ls .cov*
>> >> > ls: cannot access .cov*: No such file or directory
>> >> > make[1]: *** [check] Error 2
>> >> > make[1]: Leaving directory `/vdsm/tests'
>> >>
>> >> That was me, sorry. This should solve it:
>> >> https://gerrit.ovirt.org/#/c/91925/
>> >
>> > Thanks!
>> >
>> >> BTW, on my fc28 I see TestCountClusters.test_multiple_blocks failing
>> with
>> >>
>> >> E   Error: Command ['/usr/bin/qemu-img', 'map', '--output',
>> >> 'json', '/var/tmp/vdsm/test_multiple_blocks0/test'] failed with rc=-6
>> >> out='' err="qemu-img:
>> >> /builddir/build/BUILD/qemu-2.12.0-rc1/qemu-img.c:2680:
>> >> get_block_status: Assertion `bytes' failed.\n"
>> >>
>> >> Any idea what's that?
>> >
>> >
>> > Looks like qemu-img bug.
>> >
>> > Can you file a qemu-img bug?
>>
>> I hope Maor can translate the test to qemu-img speak.
>>
>
> Opened the following bug:
>   https://bugzilla.redhat.com/1589738
>

Adding qemu-block
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/O5CXRDSUHHHLK6D2JO7IFB5ILZCMDIZS/

[ovirt-devel] Re: [VDSM] travis tests fail consistently since Apr 14

2018-06-11 Thread Maor Lipchuk 
On Tue, Jun 5, 2018 at 9:40 AM, Dan Kenigsberg  wrote:

> On Mon, Jun 4, 2018 at 7:14 PM, Nir Soffer  wrote:
> > On Mon, Jun 4, 2018 at 6:56 PM Dan Kenigsberg  wrote:
> >>
> >> On Tue, May 8, 2018 at 11:59 AM, Nir Soffer  wrote:
> >> > There are several issues:
> >> >
> >> > 1. coverage fail after this patch:
> >> >
> >> > https://github.com/oVirt/vdsm/commit/6b905c2c134bcf344961d28eefbd05
> f2838d2ec8
> >> >
> >> > https://travis-ci.org/oVirt/vdsm/builds/366574414
> >> > ...
> >> > pwd
> >> > /vdsm/tests
> >> > ls .cov*
> >> > ls: cannot access .cov*: No such file or directory
> >> > make[1]: *** [check] Error 2
> >> > make[1]: Leaving directory `/vdsm/tests'
> >>
> >> That was me, sorry. This should solve it:
> >> https://gerrit.ovirt.org/#/c/91925/
> >
> > Thanks!
> >
> >> BTW, on my fc28 I see TestCountClusters.test_multiple_blocks failing
> with
> >>
> >> E   Error: Command ['/usr/bin/qemu-img', 'map', '--output',
> >> 'json', '/var/tmp/vdsm/test_multiple_blocks0/test'] failed with rc=-6
> >> out='' err="qemu-img:
> >> /builddir/build/BUILD/qemu-2.12.0-rc1/qemu-img.c:2680:
> >> get_block_status: Assertion `bytes' failed.\n"
> >>
> >> Any idea what's that?
> >
> >
> > Looks like qemu-img bug.
> >
> > Can you file a qemu-img bug?
>
> I hope Maor can translate the test to qemu-img speak.
>

Opened the following bug:
  https://bugzilla.redhat.com/1589738
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/QV633YH42MZ2NKBALQFUQ7TNTVLY5JRG/

[ovirt-devel] Re: [VDSM] travis tests fail consistently since Apr 14

2018-06-04 Thread Dan Kenigsberg 
On Mon, Jun 4, 2018 at 7:14 PM, Nir Soffer  wrote:
> On Mon, Jun 4, 2018 at 6:56 PM Dan Kenigsberg  wrote:
>>
>> On Tue, May 8, 2018 at 11:59 AM, Nir Soffer  wrote:
>> > There are several issues:
>> >
>> > 1. coverage fail after this patch:
>> >
>> > https://github.com/oVirt/vdsm/commit/6b905c2c134bcf344961d28eefbd05f2838d2ec8
>> >
>> > https://travis-ci.org/oVirt/vdsm/builds/366574414
>> > ...
>> > pwd
>> > /vdsm/tests
>> > ls .cov*
>> > ls: cannot access .cov*: No such file or directory
>> > make[1]: *** [check] Error 2
>> > make[1]: Leaving directory `/vdsm/tests'
>>
>> That was me, sorry. This should solve it:
>> https://gerrit.ovirt.org/#/c/91925/
>
> Thanks!
>
>> BTW, on my fc28 I see TestCountClusters.test_multiple_blocks failing with
>>
>> E   Error: Command ['/usr/bin/qemu-img', 'map', '--output',
>> 'json', '/var/tmp/vdsm/test_multiple_blocks0/test'] failed with rc=-6
>> out='' err="qemu-img:
>> /builddir/build/BUILD/qemu-2.12.0-rc1/qemu-img.c:2680:
>> get_block_status: Assertion `bytes' failed.\n"
>>
>> Any idea what's that?
>
>
> Looks like qemu-img bug.
>
> Can you file a qemu-img bug?

I hope Maor can translate the test to qemu-img speak.
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/IQGKHMLUT2EG3JZYINWLA5Z6QSKLIUM6/

[ovirt-devel] Re: [VDSM] travis tests fail consistently since Apr 14

2018-06-04 Thread Nir Soffer 
On Mon, Jun 4, 2018 at 6:56 PM Dan Kenigsberg  wrote:

> On Tue, May 8, 2018 at 11:59 AM, Nir Soffer  wrote:
> > There are several issues:
> >
> > 1. coverage fail after this patch:
> >
> https://github.com/oVirt/vdsm/commit/6b905c2c134bcf344961d28eefbd05f2838d2ec8
> >
> > https://travis-ci.org/oVirt/vdsm/builds/366574414
> > ...
> > pwd
> > /vdsm/tests
> > ls .cov*
> > ls: cannot access .cov*: No such file or directory
> > make[1]: *** [check] Error 2
> > make[1]: Leaving directory `/vdsm/tests'
>
> That was me, sorry. This should solve it:
> https://gerrit.ovirt.org/#/c/91925/

Thanks!

BTW, on my fc28 I see TestCountClusters.test_multiple_blocks failing with
>
> E   Error: Command ['/usr/bin/qemu-img', 'map', '--output',
> 'json', '/var/tmp/vdsm/test_multiple_blocks0/test'] failed with rc=-6
> out='' err="qemu-img:
> /builddir/build/BUILD/qemu-2.12.0-rc1/qemu-img.c:2680:
> get_block_status: Assertion `bytes' failed.\n"
>
> Any idea what's that?
>

Looks like qemu-img bug.

Can you file a qemu-img bug?

Nir
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ZX27S6TVZ64EEIZIPNPRCX3MNEZQWUIW/

[ovirt-devel] Re: [VDSM] travis tests fail consistently since Apr 14

2018-06-04 Thread Dan Kenigsberg 
On Tue, May 8, 2018 at 11:59 AM, Nir Soffer  wrote:
> There are several issues:
>
> 1. coverage fail after this patch:
> https://github.com/oVirt/vdsm/commit/6b905c2c134bcf344961d28eefbd05f2838d2ec8
>
> https://travis-ci.org/oVirt/vdsm/builds/366574414
> ...
> pwd
> /vdsm/tests
> ls .cov*
> ls: cannot access .cov*: No such file or directory
> make[1]: *** [check] Error 2
> make[1]: Leaving directory `/vdsm/tests'

That was me, sorry. This should solve it: https://gerrit.ovirt.org/#/c/91925/

BTW, on my fc28 I see TestCountClusters.test_multiple_blocks failing with

E   Error: Command ['/usr/bin/qemu-img', 'map', '--output',
'json', '/var/tmp/vdsm/test_multiple_blocks0/test'] failed with rc=-6
out='' err="qemu-img:
/builddir/build/BUILD/qemu-2.12.0-rc1/qemu-img.c:2680:
get_block_status: Assertion `bytes' failed.\n"

Any idea what's that?
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/D7J6ZM7PIPLLHB2LTDXDR7TH6N3USU62/

[ovirt-devel] Re: [VDSM] travis tests fail consistently since Apr 14

2018-05-31 Thread Barak Korren 
On 31 May 2018 at 13:00, Milan Zamazal  wrote:

> Nir Soffer  writes:
>
> > I know that new ovirt CI solved some of the issues, but nobody sent
> > patches to convert vdsm to the new standard yet.
>
> I asked Barak about possible Vdsm conversion at his deep dive and he
> responded that the new CI may need more real-use testing before projects
> such as Vdsm switch.  It's a couple of weeks since then and if there are
> no problems with projects that already use it (such as oVirt system
> tests), maybe we should start working on a conversion patch?
>

Let me clarify what I said back then a bit - since engine and VDSM are the
two big flagship projects, I want then to be the last projects to be
converted. So its not a matter of time its a matter of converting all the
other projects first.

Now the thing is, we will not do this on our own - maintainers need to be
in the loop as we move projects, so while we do want to be proactive about
this, given the other task load we have, things work best when the
maintainers actively approach us as some like the ovirt-provider-ovn
maintainers did.

So please if you're a small-ish project maintainer shoot an email to
infra-supp...@ovirt.org asking your project to be covered and then monitor
the jira ticket. The actual setup takes just a few minutes and we will use
the Jira ticket to update you on progress and rely any project-specific
questions you may have.



> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-
> guidelines/
> List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/
> message/BI2TZYNRFSYFZEKQJHZMDV5AKY2DF5QZ/
>



-- 
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/KDEHVDUSN6RSRM23IS4A2A4H5AOJGDMF/

[ovirt-devel] Re: [VDSM] travis tests fail consistently since Apr 14

2018-05-31 Thread Milan Zamazal 
Nir Soffer  writes:

> I know that new ovirt CI solved some of the issues, but nobody sent
> patches to convert vdsm to the new standard yet.

I asked Barak about possible Vdsm conversion at his deep dive and he
responded that the new CI may need more real-use testing before projects
such as Vdsm switch.  It's a couple of weeks since then and if there are
no problems with projects that already use it (such as oVirt system
tests), maybe we should start working on a conversion patch?
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/BI2TZYNRFSYFZEKQJHZMDV5AKY2DF5QZ/

[ovirt-devel] Re: [VDSM] travis tests fail consistently since Apr 14

2018-05-31 Thread Nir Soffer 
On Thu, May 31, 2018 at 10:34 AM Sandro Bonazzola 
wrote:

> 2018-05-16 17:12 GMT+02:00 Sandro Bonazzola :
>
>>
>>
>> 2018-05-16 15:20 GMT+02:00 Nir Soffer :
>>
>>> Ping
>>>
>>>
>> There's ongoing discussion about the real need of having travis testing.
>> What do we test in travis that Jenkins is not testing already?
>>
>
Travis give us several advantages:
- Generally more reliable, less tests marked broken on travis. I think the
key is
  having fresh vm per build. I wish we had that in ovirt CI.
- Typically faster. Here is a random example:
  travis builds:
  - https://travis-ci.org/oVirt/vdsm/builds/386053193

  8 minutes
  gerrit builds:
  - https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc27-x86_64/3571/
  - https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/23748/
  20 minutes
- Need one url to refer to a build, instead of one url per platform
- Easier to setup and maintain - one yaml file, one dockerfile per platform
- We control the project configuration
- Easy to test project configuration - no need to merge to test a change
- Simpler, we run in a docker image, updated when the base image updates
  or manually by building from dockerfiles in vdsm source
- Easier to get contributions, lot of people know travis
- Anyone can run the tests in travis, no need for whitelists, just fork vdsm
  and enable travis builds in your private account
- Easy to test multiple python versions, even nighties
- Travis errors never fail builds, and sometimes even restart a build
   it understands the difference between "error - could not run the tests",
 "failure - some tests failed", and "success - no test failed".
  ovirt CI sometimes fail successful build because it could not clean up
after itself.
- Running on another platform (Ubuntu) - helps to reveal bugs that sometimes
  are hidden on CentOS/Fedora.
  (example:
https://github.com/nirs/sanlock/commit/c7fd1b6915c470c6beb191a79c741fb1e6ca9575
)
- No vendor lock-in (I don't like to depend on single CI provider)
- I enjoy using it, I don't enjoy gerrit and jenkins

I know that new ovirt CI solved some of the issues, but nobody sent
patches to convert vdsm to the new standard yet.

Issues with travis:
- no integration with gerrit, so people tend to break it
  it wold be nice if we could trigger travis build for every patch, and fail
  the build if travis failed
- need too much manual image rebuilding
- image rebuilds are slow (cost of a free docker account)
- we depend on 3 different services: travis, github, and docker - for
single build


> Travis CI is still failing.
> https://travis-ci.org/oVirt/vdsm/jobs/386053194
>
>
> OK (SKIP=63)
> mv .coverage .coverage-nose-py2
> mv: cannot stat '.coverage': No such file or directory
> make[1]: *** [check] Error 1
>
> make[1]: Leaving directory `/vdsm/tests'
>
> ERROR: InvocationError: '/usr/bin/make -C tests check'
>
>
>
I think this is the cause: https://github.com/oVirt/vdsm/
commit/6b905c2c134bcf344961d28eefbd05f2838d2ec8

This also seems to be broken when running make locally.


>
>
> def _run_cmd(cmd, cwd=None):
> rc, out, err = commands.execCmd(cmd, raw=True, cwd=cwd)
> if rc != 0:
> >   raise cmdutils.Error(cmd, rc, out, err)
> E   Error: Command ['/usr/bin/qemu-img', 'info', '--output', 'json', 
> '-U', '/var/tmp/tmp89QFPD/img.img'] failed with rc=1 out='' err="qemu-img: 
> unrecognized option '-U'\nTry 'qemu-img --help' for more information\n"
> ../lib/vdsm/storage/qemuimg.py:399: Error
>
>
This means we are running old qemu, need to update our images.
I guess this broken in the centos build?


> this happen 3 times in the job causing the result to be:
>
>  3 failed, 1387 passed, 7 skipped, 125 deselected, 1 xfailed, 9 xpassed in 
> 126.99 seconds
> ERROR: InvocationError: '/vdsm/tests/py-watch 600 pytest -m not (slow or 
> stress) --durations=10 --cov=vdsm.storage 
> --cov-report=html:htmlcov-storage-py27 storage'
>
>
> Also:
>
> storage-py36 create: /vdsm/.tox/storage-py36
> ERROR: InterpreterNotFound: python3.6
>
>
This is just a warning that python 3.6 is not available, expected when
running on centos.

Maybe we can eliminate these errors in the CI, since we know what
python version should be tested for every image.

Nir


>
>
> There are also several other errors.
>
>
>
>
>
>
>>
>>
>>
>>> On Tue, May 8, 2018 at 11:59 AM Nir Soffer  wrote:
>>>
 There are several issues:

 1. coverage fail after this patch:

 https://github.com/oVirt/vdsm/commit/6b905c2c134bcf344961d28eefbd05f2838d2ec8

 https://travis-ci.org/oVirt/vdsm/builds/366574414
 ...
 pwd
 /vdsm/tests
 ls .cov*
 ls: cannot access .cov*: No such file or directory
 make[1]: *** [check] Error 2
 make[1]: Leaving directory `/vdsm/tests'

 2. pywatch_test - gdb not installed

 We need to add gdb and install install python-debuginfo p

[ovirt-devel] Re: [VDSM] travis tests fail consistently since Apr 14

2018-05-31 Thread Sandro Bonazzola 
2018-05-16 17:12 GMT+02:00 Sandro Bonazzola :

>
>
> 2018-05-16 15:20 GMT+02:00 Nir Soffer :
>
>> Ping
>>
>>
> There's ongoing discussion about the real need of having travis testing.
> What do we test in travis that Jenkins is not testing already?
>


Travis CI is still failing.
https://travis-ci.org/oVirt/vdsm/jobs/386053194


OK (SKIP=63)
mv .coverage .coverage-nose-py2
mv: cannot stat '.coverage': No such file or directory
make[1]: *** [check] Error 1
make[1]: Leaving directory `/vdsm/tests'
ERROR: InvocationError: '/usr/bin/make -C tests check'




def _run_cmd(cmd, cwd=None):
rc, out, err = commands.execCmd(cmd, raw=True, cwd=cwd)
if rc != 0:
>   raise cmdutils.Error(cmd, rc, out, err)
E   Error: Command ['/usr/bin/qemu-img', 'info', '--output',
'json', '-U', '/var/tmp/tmp89QFPD/img.img'] failed with rc=1 out=''
err="qemu-img: unrecognized option '-U'\nTry 'qemu-img --help' for
more information\n"
../lib/vdsm/storage/qemuimg.py:399: Error


this happen 3 times in the job causing the result to be:

 3 failed, 1387 passed, 7 skipped, 125 deselected, 1 xfailed, 9
xpassed in 126.99 seconds
ERROR: InvocationError: '/vdsm/tests/py-watch 600 pytest -m not (slow
or stress) --durations=10 --cov=vdsm.storage
--cov-report=html:htmlcov-storage-py27 storage'


Also:

storage-py36 create: /vdsm/.tox/storage-py36
ERROR: InterpreterNotFound: python3.6




There are also several other errors.






>
>
>
>> On Tue, May 8, 2018 at 11:59 AM Nir Soffer  wrote:
>>
>>> There are several issues:
>>>
>>> 1. coverage fail after this patch:
>>> https://github.com/oVirt/vdsm/commit/6b905c2c134bcf344961d28
>>> eefbd05f2838d2ec8
>>>
>>> https://travis-ci.org/oVirt/vdsm/builds/366574414
>>> ...
>>> pwd
>>> /vdsm/tests
>>> ls .cov*
>>> ls: cannot access .cov*: No such file or directory
>>> make[1]: *** [check] Error 2
>>> make[1]: Leaving directory `/vdsm/tests'
>>>
>>> 2. pywatch_test - gdb not installed
>>>
>>> We need to add gdb and install install python-debuginfo package on
>>> the test images.
>>>
>>> self = 
>>> def test_timeout(self):
>>> rc, out, err = exec_cmd(['./py-watch', '0.1', 'sleep', '10'])
>>> assert b'Watched process timed out' in out
>>> >   assert rc == 128 + signal.SIGTERM
>>> E   assert 1 == (128 + 15)
>>> E+  where 15 = signal.SIGTERM
>>> pywatch_test.py:45: AssertionError
>>> -- Captured log call
>>> ---
>>> cmdutils.py151 DEBUG./py-watch 0.1 sleep 10 (cwd
>>> None)
>>> cmdutils.py159 DEBUGFAILED:  = 'Traceback (most
>>> recent call last):\n  File "./py-watch", line 59, in \n
>>> dump_trace(watched_proc)\n  File "./py-watch", line 32, in dump_trace\n
>>> \'thread apply all py-bt\'])\n  File 
>>> "/usr/lib64/python2.7/site-packages/subprocess32.py",
>>> line 575, in call\np = Popen(*popenargs, **kwargs)\n  File
>>> "/usr/lib64/python2.7/site-packages/subprocess32.py", line 822, in
>>> __init__\nrestore_signals, start_new_session)\n  File
>>> "/usr/lib64/python2.7/site-packages/subprocess32.py", line 1567, in
>>> _execute_child\nraise child_exception_type(errno_num,
>>> err_msg)\nOSError: [Errno 2] No such file or directory: \'gdb\'\n';  = 1
>>>
>>> Nir
>>>
>>
>> ___
>> Devel mailing list -- devel@ovirt.org
>> To unsubscribe send an email to devel-le...@ovirt.org
>>
>>
>
>
> --
>
> SANDRO BONAZZOLA
>
> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
>
> Red Hat EMEA 
>
> sbona...@redhat.com
> 
> 
>



-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D

Red Hat EMEA 

sbona...@redhat.com


___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/K4GTCQG5PDPKZZWTJSWRFSAW3XHZSPHI/

[ovirt-devel] Re: [VDSM] travis tests fail consistently since Apr 14

2018-05-16 Thread Sandro Bonazzola 
2018-05-16 15:20 GMT+02:00 Nir Soffer :

> Ping
>
>
There's ongoing discussion about the real need of having travis testing.
What do we test in travis that Jenkins is not testing already?



> On Tue, May 8, 2018 at 11:59 AM Nir Soffer  wrote:
>
>> There are several issues:
>>
>> 1. coverage fail after this patch:
>> https://github.com/oVirt/vdsm/commit/6b905c2c134bcf344961d28eefbd05
>> f2838d2ec8
>>
>> https://travis-ci.org/oVirt/vdsm/builds/366574414
>> ...
>> pwd
>> /vdsm/tests
>> ls .cov*
>> ls: cannot access .cov*: No such file or directory
>> make[1]: *** [check] Error 2
>> make[1]: Leaving directory `/vdsm/tests'
>>
>> 2. pywatch_test - gdb not installed
>>
>> We need to add gdb and install install python-debuginfo package on
>> the test images.
>>
>> self = 
>> def test_timeout(self):
>> rc, out, err = exec_cmd(['./py-watch', '0.1', 'sleep', '10'])
>> assert b'Watched process timed out' in out
>> >   assert rc == 128 + signal.SIGTERM
>> E   assert 1 == (128 + 15)
>> E+  where 15 = signal.SIGTERM
>> pywatch_test.py:45: AssertionError
>> -- Captured log call
>> ---
>> cmdutils.py151 DEBUG./py-watch 0.1 sleep 10 (cwd None)
>> cmdutils.py159 DEBUGFAILED:  = 'Traceback (most
>> recent call last):\n  File "./py-watch", line 59, in \n
>> dump_trace(watched_proc)\n  File "./py-watch", line 32, in dump_trace\n
>> \'thread apply all py-bt\'])\n  File 
>> "/usr/lib64/python2.7/site-packages/subprocess32.py",
>> line 575, in call\np = Popen(*popenargs, **kwargs)\n  File
>> "/usr/lib64/python2.7/site-packages/subprocess32.py", line 822, in
>> __init__\nrestore_signals, start_new_session)\n  File
>> "/usr/lib64/python2.7/site-packages/subprocess32.py", line 1567, in
>> _execute_child\nraise child_exception_type(errno_num,
>> err_msg)\nOSError: [Errno 2] No such file or directory: \'gdb\'\n';  = 1
>>
>> Nir
>>
>
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@ovirt.org
>
>


-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D

Red Hat EMEA 

sbona...@redhat.com


___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org

[ovirt-devel] Re: [VDSM] travis tests fail consistently since Apr 14

2018-05-16 Thread Nir Soffer 
Ping

On Tue, May 8, 2018 at 11:59 AM Nir Soffer  wrote:

> There are several issues:
>
> 1. coverage fail after this patch:
>
> https://github.com/oVirt/vdsm/commit/6b905c2c134bcf344961d28eefbd05f2838d2ec8
>
> https://travis-ci.org/oVirt/vdsm/builds/366574414
> ...
> pwd
> /vdsm/tests
> ls .cov*
> ls: cannot access .cov*: No such file or directory
> make[1]: *** [check] Error 2
> make[1]: Leaving directory `/vdsm/tests'
>
> 2. pywatch_test - gdb not installed
>
> We need to add gdb and install install python-debuginfo package on
> the test images.
>
> self = 
> def test_timeout(self):
> rc, out, err = exec_cmd(['./py-watch', '0.1', 'sleep', '10'])
> assert b'Watched process timed out' in out
> >   assert rc == 128 + signal.SIGTERM
> E   assert 1 == (128 + 15)
> E+  where 15 = signal.SIGTERM
> pywatch_test.py:45: AssertionError
> -- Captured log call
> ---
> cmdutils.py151 DEBUG./py-watch 0.1 sleep 10 (cwd None)
> cmdutils.py159 DEBUGFAILED:  = 'Traceback (most
> recent call last):\n  File "./py-watch", line 59, in \n
> dump_trace(watched_proc)\n  File "./py-watch", line 32, in dump_trace\n
> \'thread apply all py-bt\'])\n  File
> "/usr/lib64/python2.7/site-packages/subprocess32.py", line 575, in call\n
>   p = Popen(*popenargs, **kwargs)\n  File
> "/usr/lib64/python2.7/site-packages/subprocess32.py", line 822, in
> __init__\nrestore_signals, start_new_session)\n  File
> "/usr/lib64/python2.7/site-packages/subprocess32.py", line 1567, in
> _execute_child\nraise child_exception_type(errno_num,
> err_msg)\nOSError: [Errno 2] No such file or directory: \'gdb\'\n';  = 1
>
> Nir
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org