[Koha-bugs] [Bug 18055] Speed up '00-strict.t' test

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Thu Mar 9 13:37:05 CET 2017


https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18055

Olli-Antti Kivilahti <olli-antti.kivilahti at jns.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |olli-antti.kivilahti at jns.fi

--- Comment #19 from Olli-Antti Kivilahti <olli-antti.kivilahti at jns.fi> ---
Hi!

Pretty good improvement.

What concerns me is how well does this module detect the available CPU cores?

For example on LXC all the cores are visible to the test runner.

There can be resource limits, but we might get a situation where we fork 32
test runners because the LXC container is ran on a server with 32 cores.
However resource limits prevent utilization of more than 4 on this
LXC-container.

This is not good.

Maybe a better solution would be to accelerate the whole test running
infrastructure. I am not seeing anything in t or $KOHA_PATH which would allow
to easily run all Koha's tests, but I have been working on something like Bug
18238.

Parallelizing the test runs makes sense in this bigger context, but needs
multiple parallel test databases and KOHA_CONF's and is generally a big hassle
and prone to all kinds of strange race condition errors.

Maybe it is better to parallellize tests from infrastructure using your DevOps
(TM) build pipeline and run tests on multiple Koha-intances?

-- 
You are receiving this mail because:
You are watching all bug changes.


More information about the Koha-bugs mailing list