I'm pretty sure the merging of #916 is the culprit: now the test suite runs a simple snippet with run -p, which opens the profiler information in the pager. This means that the test suite stops until the user manually closes that pager.
It should always be possible to run the test suite in 100% automated fashion and have it complete. @takluyver, do you think you could have a look? If not I'll do it, but I'm running out of ipython time for the next few days...
One solution is to keep the current run -p test, but temporarily change the pager in that test to be the simple printing pager. In fact, this is probably what we should do unconditionally to the global instance we start in globalipapp for the test suite: it makes no sense at all in the test suite to open the real pager, so we might as well use the dumb print-only pager always in the test suite. This will take care of this problem ever reappearing again in the future triggered by a different codepath.
Disable the pager for the test suite.
Should fix gh-949
BTW, @takluyver, I never pinged back on this. Many thanks, I can confirm that it does indeed fix this big annoyance!
@fperez: You're welcome!