The integration tests take ages (not that much anymore, but still) #45
Comments
|
Today I have massively sped up our test suite execution in mock from 100 seconds to 15 seconds by using The problem is that network is disabled in mock and ansible times out when gathering certain facts. Since you don't use any facts in |
|
Thanks for the tip. I'll do some testing, but our mock has networking enabled. |
|
As is (two measurements): |
|
Disabling gathering facts: I don't think there's any difference. But I can make more measurements over night. |
|
If it has networking enabled, then no, there won't be any significant speed up. |
|
I have an idea how to make the mock calls parallel runnable. If it works, we can try to run the testsuite with pytest-xdist. |
|
OK, so problem with xdist is that it doesn't group by fixture, so the parallelism is completely useless. |
This is an attempt to fix fedora-python#45 It does the following: * uses pytest-xdist to paralelize the tests (3 workers) * utilizes custom scheduler that splits the tests acroding to the fixture name * this is needed not to use 1 fixture on multiple workers see pytest-dev/pytest-xdist#18 * use parametrize an all integration tests to enbale our hackish scheduler * mock now creates the roots in pwd (not to pollute the filesystem on /) * note that the roots can take sveral GBs
This is an attempt to fix fedora-python#45 It does the following: * uses pytest-xdist to paralellize the tests (3 workers) * utilizes custom scheduler that splits the tests according to the fixture name * this is needed not to use 1 fixture on multiple workers see pytest-dev/pytest-xdist#18 * use parametrize an all integration tests to enable our hackish scheduler * mock now creates the roots in pwd (not to pollute the filesystem on /) * note that the roots can take several GBs
|
Ok, this is now better but not perfect. |
hroncok
changed the title
|
Closing, Taskotron goes EOL on 2020-04-30. |
The integration tests were parallelized in #62 but this keeps open because the time is still not ideal.
Original issue follows:
(Especially after #44.)
The text was updated successfully, but these errors were encountered: