Re: [ovirt-devel] Vdsm tests are 4X times faster on travis
On Mon, Dec 5, 2016 at 12:48 PM, Yaniv Kaul <ykaul(a)redhat.com> wrote:
On Mon, Dec 5, 2016 at 9:59 AM, Barak Korren <bkorren(a)redhat.com> wrote:
>
> > Here are builds that do not change the build system:
> > -
> > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/5767/con...:
> > 10:07
> > -
> > http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/4157/console:
> > 10:16
> >
> > So we about 2X times faster now.
>
> Awesome! also for fc24:
>
> 22:11:22 Init took 73 seconds
>
> 22:13:45 Install packages took 143 seconds
>
> So 3m 36s, our pending patches can probably bring that down to around
> 20s. That will get us to around 7m...
> Maybe we could shave some more seconds off by optimizing the git clone
> and making some of the cleanups happen less frequently.
> (It seems we spend 16s total outside of mock_runner.sh, so perhaps not
> much to gain there).
>
> So any more ideas where we can get extra 2-3m?
Can we run the tests in parallel in nose[1] ?
We don't want to go there, lot of tests are not safe when run concurrently.
If we want this we need to check all tests and mark those that can be
run in parallel
and then find how to do this in the test framework.
Anyway we don't want to use nose, it is a dead project, and we want to move
to pytest.
We already use pytest for the import tests, see "tox -e imports"
Y.
[1]
http://nose.readthedocs.io/en/latest/doc_tests/test_multiprocess/multipro...
>
>
> Things we didn`t try yet:
> 1. Ensure all downloads happen through the proxy (there is a patch
> pending, but some tweaking in check_patch.sh may be needed as well)
> 2. Run mock in tmpfs (it has a plugin for that)
> 3. Avoid setting some FS attributes on files (mock is configured for
> that but we don't install the OS package needed to make that actually
> work)
>
> Nut sure any of the above will provide significant gains though.
>
> --
> Barak Korren
> bkorren(a)redhat.com
> RHCE, RHCi, RHV-DevOps Team
> https://ifireball.wordpress.com/
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel