Currently, the execution time of test jobs in CI is unbalanced. For example, in this build, the job
CI_TARGET=valgrind-parvorm TEST=examples.frm
took 27 minutes, in which running test cases spent 20 minutes. Typically, this job (or CI_TARGET=valgrind-parvorm TEST=fixes.frm) remains running in the end of the whole set. Because it seems that 4 jobs can concurrently run on Travis CI, splitting it further may make the total CI time shorter.
Currently, the execution time of test jobs in CI is unbalanced. For example, in this build, the job
took 27 minutes, in which running test cases spent 20 minutes. Typically, this job (or
CI_TARGET=valgrind-parvorm TEST=fixes.frm
) remains running in the end of the whole set. Because it seems that 4 jobs can concurrently run on Travis CI, splitting it further may make the total CI time shorter.Perhaps, in a spirit of pytest-split-tests, it could be split into
The same for
CI_TARGET=valgrind-parvorm TEST=fixes.frm
.