[JIRA] (OVIRT-902) Speed up mock_runner.sh setup time by using caches.

[Yaniv Kaul (oVirt JIRA)]

    [ https://ovirt-jira.atlassian.net/browse/OVIRT-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23804#comment-23804 ] 

Yaniv Kaul commented on OVIRT-902:
----------------------------------

1. I'm not sure if it's here or requires a different ticket, but this is SLOW (taken from http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/5101/consoleFull ):

*00:01:28.338* INFO: installing package(s): autoconf automake gdb git libguestfs-tools-c libselinux-python3 libvirt-python3 m2crypto make mom openvswitch policycoreutils-python PyYAML python-blivet python-coverage python2-decorator python-devel python-inotify python-ioprocess python-mock python-netaddr python-pthreading python-setuptools python-six python-requests python3-decorator python3-netaddr python3-nose python3-six python3-yaml rpm-build sanlock-python sudo yum yum-utils
*00:03:48.999* INFO: None

2:20 to install packages, is VERY slow.


2. Then there are the pip stuff - which probably are also going somewhere off to the 'net:
00:03:52.839 + easy_install pip
...
00:03:53.401 + pip install -U tox==2.1.1
...
00:03:55.843   Downloading pluggy-0.3.1-py2.py3-none-any.whl
00:03:55.868 Installing collected packages: virtualenv, py, pluggy, tox
00:03:56.223 Successfully installed pluggy-0.3.1 py-1.4.31 tox-2.1.1 virtualenv-15.1.0

So only 4 seconds, but probably not needed at all.

3. Why not set locale?
00:03:56.670 + ./autogen.sh --system --enable-hooks --enable-vhostmd
00:03:56.678 perl: warning: Setting locale failed.
00:03:56.678 perl: warning: Please check that your locale settings:
00:03:56.679 	LANGUAGE = (unset),
00:03:56.679 	LC_ALL = (unset),
00:03:56.679 	LANG = "en_US.UTF-8"

4. The 5 seconds here are probably due to slow storage!
00:04:05.096 client/Makefile.am:23: installing 'build-aux/py-compile'
00:04:10.239 Running ./configure with --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=/usr/lib64 --enable-hooks --enable-vhostmd

5. This is also going out to the Internet?
00:04:14.989 + debuginfo-install -y python
...
00:04:30.879   glibc-debuginfo-common.x86_64 0:2.23.1-11.fc24         

6. Again some more deps:
00:05:23.621 tox -e tests
00:05:23.912 tests create: /home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/.tox/tests
00:05:29.991 tests installdeps: nose==1.3.7

7. it's not clear if the nose tests are running in parallel. Is that supported by VDSM tests?
8. Not sure what is going on here:
00:09:34.017 + coverage html -d /home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/exported-artifacts/htmlcov
00:09:49.213 + popd
00:09:49.213 ~
00:09:49.213 + shopt -s extglob
00:09:49.213 + git diff-tree --no-commit-id --name-only -r HEAD
00:09:49.213 + egrep --quiet 'vdsm.spec.in|Makefile.am'
00:19:07.994 Took 915 seconds


> Speed up mock_runner.sh setup time by using caches.
> ---------------------------------------------------
>
>                 Key: OVIRT-902
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-902
>             Project: oVirt - virtualization made easy
>          Issue Type: Improvement
>            Reporter: Barak Korren
>            Assignee: infra
>            Priority: High
>              Labels: mock, mock_runner.sh, standard-ci
>
> We've already known that setting up mock takes a while, but mock has some built-in caching features that should allow us to speed this up.
> We need to ensure those features are enabled by mock_runner.sh. The mock options to look at are:
> * root_cache_enable
> * yum_cache_enable
> Both these options should be set to true in the mock chroot config file.
> We've been using these option downstream in minimead and the vdsm build scripts, so they should be safe to use.



--
This message was sent by Atlassian JIRA
(v1000.610.2#100023)