The issue was reported in AS7-5350 which points to a CLI testcase that fails on windows.

The test starts a CLI process and deliberately specifies a wrong port for the controller expecting a failure during connection. The CLI sends a read-attribute operation request on connect to make sure the connection is working. The test is waiting for a response from the controller for 10 sec and then times out. The time out of the ModelControllerClient is 5 sec. The test still fails after 10 sec time out but the error output stream of the CLI process does contain the stack trace of the expected exception, i.e. that the controller was not available at the specified address.

When the testcase times out, it destroys the CLI process, perhaps, this triggers some actions and the exception is finally thrown and the stack trace gets logged but it's too late.