Per e-mail on 30 April, 2018, the problem seems to have been caused by an SSH session disconnecting during the test (which is common) combined with NOT using the "screen" utility. Under these circumstances, the test suite terminated the test run, causing the failure. The solution is to use "screen" or run the tests at the console. I'm going to leave this bug report open, since better robustness to this condition is desirable.
Per e-mail on 30 April, 2018, the problem seems to have been caused by an SSH session disconnecting during the test (which is common) combined with NOT using the "screen" utility. Under these circumstances, the test suite terminated the test run, causing the failure. The solution is to use "screen" or run the tests at the console. I'm going to leave this bug report open, since better robustness to this condition is desirable.