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

On Thu, May 31, 2018 at 10:34 AM Sandro Bonazzola <sbonazzo(a)redhat.com&gt; wrote: 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 <https://travis-ci.org/oVirt/vdsm/builds/386053193?utm_source=github_statu... 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/c7fd1b6915c470c6beb191a79c741fb1e6... ) - 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 I think this is the cause: https://github.com/oVirt/vdsm/ commit/6b905c2c134bcf344961d28eefbd05f2838d2ec8 This also seems to be broken when running make locally. This means we are running old qemu, need to update our images. I guess this broken in the centos build? 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