Provided you are on a *nix system (I don't know what a CI system is) you can try redirecting the output of the install/tests to a file something like: runtests &> logfile or better, initiate screen and run the install scripts through that and perhaps put it to the background before reaching the critical point.
Could it be that some special characters from the tests mess your shell and/or connection - some control sequences?
In reply to Re: How do I make a Perl install NOT use the test harness?
by bliako
in thread How do I make a Perl install NOT use the test harness?
by mpersico
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |