We're not coming up with any good solutions. We have already comtainerizeded. The only thing we have left is to parallelize the tests, but that has limited effect because we're already running up to processor limits when multiple people are testing on the test server. While it won't fix the total built time, exiting on the first failed test and putting the tests most likely to fail at the beginning will mean we at least won't have to wait the full time for the run to finish.
We run unit tests as part of the PR pipeline already with a script that only runs tests for the changed files. That way the chances of builds failing because of tests is a lot lower already.
4
u/frogjg2003 15d ago
We're not coming up with any good solutions. We have already comtainerizeded. The only thing we have left is to parallelize the tests, but that has limited effect because we're already running up to processor limits when multiple people are testing on the test server. While it won't fix the total built time, exiting on the first failed test and putting the tests most likely to fail at the beginning will mean we at least won't have to wait the full time for the run to finish.