[SSSD] [PATCH] CI: Allow disabling distro-(in)dependent tests
Nikolai Kondrashov
Nikolai.Kondrashov at redhat.com
Wed Sep 3 13:59:01 UTC 2014
On 09/03/2014 04:40 PM, Lukas Slebodnik wrote:
> On (03/09/14 16:06), Nikolai Kondrashov wrote:
>> It does sometimes. Take a look at this:
>>
>> http://sssd-ci.duckdns.org/logs/job/0/19/rhel7/ci.html
>> http://sssd-ci.duckdns.org/logs/job/0/21/rhel7/ci.html
>>
> I am not sure what is wrong.
> I have 4 CPUs on my machine and rpms are already cached in /var/cache/mock/
> I don't have SSD.
>
> [build at host mock]$ time mock --root epel-6-x86_64-ding-libs --resultdir
> . --rebuild sssd-1.12.1-0.el6.src.rpm
> //snip
>
> real 1m50.537s
> user 1m54.073s
> sys 0m15.984s
>
> and with empty cache
> [build at host mock]$ time mock --root epel-6-x86_64-ding-libs --resultdir
> . --rebuild sssd-1.12.1-0.el6.src.rpm
> //snip
>
> real 6m55.672s
> user 4m22.671s
> sys 0m27.573s
Well, on a shared host with lots of VMs anything can happen, I suppose.
Especially if five mock builds start rebuilding their cache at once.
>> You don't exactly provide a tip here, but I'll assume that you meant some
>> hosts don't need to run mock builds. However, the whole CI run will be as long
>> as the longest host run, which will be one of those which include mock builds,
>> so this doesn't exactly speed up getting results.
>>
> I meant to call mock just one on each distro
>
> epel6 mock --root epel-6-$ARCH ...
> epel7 mock --root epel-7-$ARCH ...
> fedora20 mock --root fedora-20-$ARCH ...
> fedora20 mock --root fedora-21-$ARCH ...
> fedora-rawhide mock --root fedora-rawhide-$ARCH ...
Yes, that could be one solution, especially if the caching, which I try to
avoid with the other patch, is really such a big overhead.
The question is, do we really need so many mock builds or not? And also what
are we going to do with Clang?
It is also possible that there will be more distro-independent tests in the
future. For example, coding style check. So, I think having a dedicated host
for distro-independent tasks will still be useful.
Now, with caching avoided and tmpfs mock plugin enabled I managed to get each
mock build down to 2-3 minutes:
http://sssd-ci.duckdns.org/logs-test/job/0/16/common/ci.html
and the overall rigorous (full) run time down to 15 minutes.
However, I'm not sure we'll be able to afford the increased memory
requirements of the tmpfs plugin on all the hosts.
Nick
More information about the sssd-devel
mailing list