Some tests are very slow in coverage job
Depending on which runner the nightly coverage job ends up on, it might fail because some of the tests are extremely slow and time out:
- DragForceSpherePSMRefinementSC1W1FuncTest
- MeshInitializationTestDbg1P1
- MeshInitializationTestDbg2P1
- MeshInitializationTestDbg2P2
- PE_RAYTRACING
- SuViscoelasticityTest
There is one more that just barely completes before hitting the 3000-second timeout:
- ComplexGeometry
The following runners are evidently too slow to complete the coverage job:
- i10guest2
- i10swarm1
- i10swarm3
- i10swarm4
- i10swarm5
- i10swarm11
- i10swarm12
- i10swarm13
This did not happen regularly before the last week of July. Successful jobs in July ran on the following runners:
- i10guest2
- i10staff14
- i10staff43
- i10swarm2
- i10swarm6
- i10swarm7
- i10swarm8
- i10swarm12
- i10swarm13
These two lists are almost completely disjoint, so perhaps the problem can be fixed by tagging the coverage jobs to one of the faster machines. Furthermore, the slow tests should be optimized, e.g. run with fewer time steps in debug mode.