assess whether Jenkins is testing multi-rank runs appropriately - Redmine #2134
Recent bugs (e.g. #2131 and #2105) suggest that testing of multi-rank mdrun, or -npme >0 is not occurring appropriately.
(from redmine: issue id 2134, created on 2017-03-07 by mark.j.abraham, closed on 2018-01-04)
- Relations:
- relates #2131 (closed)
- relates #2105 (closed)
- relates #2164 (closed)
- Changesets:
- Revision 498a4235f7c56fc87cc1ea4117504376a3e164bb by Mark Abraham on 2017-03-17T14:16:05Z:
Limit small essentialdynamics tests to one rank
These systems are tiny, so running a single rank is all that makes sense.
The flooding systems are reasonable for normal DD.
This should help re-implement MPMD releng support.
Refs #2134
Change-Id: Id52f271d91e98f732384640a01b0db728d9a2da1
- Revision 877e93df by Mark Abraham on 2017-04-17T11:06:13Z:
Propose a post-submit matrix
A recent bug would have been prevented if some testing of
separate PME ranks had been occuring.
Extended gromacs.py to permit regressiontests to run
with separate PME ranks, and/or designated numbers of
ranks, or GPU ids.
Quieted some newly exposed warnings.
Documented more of the reasoning behind matrix choices, to help us
maintain better. Noted various TODOs for better testing coverage.
Refs #2134
Change-Id: Ib9828ca769d7a446c61fb8bb7a68128a38991aba
- Revision a2051ce44f5264643e12bd9ebb568991aeb7c9aa by Mark Abraham on 2017-06-27T16:07:22Z:
Resolve TODO for specifying npme
This meant that the pre- and post-submit matrix configs with npme=1
were not actually testing the intended MPMD path.
Refs #2134
Change-Id: I5adf0691b26d89e248d136b8d93068080014607e
- Revision 27246474de3cbb831fe045e9f08e1e43b3b623b2 by Mark Abraham on 2017-06-27T16:47:28Z:
Fix gmxtest.pl handling of GPU IDs
For example, mdrun -ntmpi 2 -gpu_id 2 would not start 2 PP ranks on
GPU ID 2, which was what we'd intended it to do. Instead, the automatic
repeater would make it run with one rank.
mdrun -ntmpi 2 -gpu_id 01 was OK though.
This change would permit a Jenkins matrix to specify any of
gcc-4.8 gpu gpu_id=1
gcc-4.8 gpu nranks=2 gpu_id=012
gcc-4.8 gpu npme=1 nranks=3 gpu_id=0
and ensures that we get the number and flavour of ranks specified.
This should mean it is no longer desirable to rerun a test case
when the number of ranks and the GPU ID choice do not work.
Refs #2134
Change-Id: Idba4a7de2069a67adb4cdf8b3e025a35d13c1f14