regressiontests/freeenergy fail (timeout) on arm
Basically the freeenergy tests take too long and cmake kills them after 1500 secs, which lead to a fail.
Fix tests that were unstable or too long
Some freeenergy tests were taking too long.
simple_search_group was unstable, so converted it and simple_search to
be better behaved. The boxes they use are uncomfortably small, so the
cutoffs need to be small also.
relative was also unstable, occasionally failing on bs_nix1004 and
another Jenkins slave around step 17. That suggests the step 10
neighbour search was not reproducible enough.
Also shortened the freenergy/relative simulation
(keeping nstdhdl with at least two nstlist calls between).
#2 Updated by Michael Shirts about 7 years ago
Sure, to reduce the size, one could do the following:
reduce nstdhdl from 100 to 20 for all of the mdp's that have longer time constants
Reduce nststep from to max 40 in all cases (rather than 60-100).
For restraints, which is a larger system and likely one of the larger costs, reduce nststep to 20.
in general, I'd like to keeo some longer, because there are errors that can show up when dhdl is a larger multiple of nstlist, and we want to get at least one extra line dhdl output beyond the first.
I'm 1) traveling right now and 2) not 100% confident on the process right now for replacing the regression tests in a way that doesn't screw up the build process, so perhaps someone else could make these changes?
#6 Updated by Erik Lindahl over 6 years ago
- Tracker changed from Bug to Feature
Changing to a feature. While it is nice if the tests complete sooner, we have never guaranteed that tests should complete within X seconds. The auto-download with CMake was a feature Roland Schulz added, but if that is causing problems our short-term option might be to disable the auto-download :-)
For now I would recommend Gentoo to disable running the extensive regressiontests automatically.