The gproc_dist_test module used the 'inparallel' EUnit macro, basically in order to improve speed. However, this seems to introduce some indeterminism. The test has been changed to 'inorder'. This revealed some bugs, some trailing DOWN messages (this probably didn't affect the 'inparallel' run, since the test cases ran in different processes).
…empty This may happen in case if rebar is used as a library.
If GPROC_DIST==false, dist tests are skipped If GPROC_DIST==true, they are attempted If GPROC_DIST not set, dist tests are run if gen_leader is found.