policy around "slow-running tests"
Hi, I'm wondering what the policies or principles are around
"slow-running" debci tests.
Currently dolfin, for instance, is catalogued as slow-running at
https://ci.debian.net/status/slow/, with its tests taking 1 hr 16 mins.
Is this considered a problem? Or should the full suite of tests just be
allowed to run?
In the case of dolfin, again for example, tests cover not only unit
tests but also run demo scripts. Most of the test time is in the demos,
which take about 15 min each full set, run 4 times over [C++,
python]×[serial, mpi] making an hour in total demo time. It would be
simple enough to run a subset of demos if we considered it important to
reduce total test time.
Drew
Reply to: