25 May
2021
25 May
'21
4:45 p.m.
Hi :) IIUC this is where the CI calls "prove" to run the tests https://gitlab.com/koha-community/koha-testing-docker/-/blob/master/files/ru... And this is the place where KOHA_PROVE_CPUS is set. https://gitlab.com/koha-community/koha-testing-docker/-/blob/master/files/ru... It's not set in ".env" file so it should use "nproc" and this calls "prove" with more than one thread. Is that really the case? I tried locally use to "prove -j 4" and I'm getting deadlocks with the database after a few minutes. And do these deadlock in tests mean that Koha can hit them while running in production? I expect the tests to fail due to messing up with each other data but a deadlock is something else. Cheers, -- Victor Grousset/tuxayo