After the build times out the final message is "Finished: ABORTED". If there was still a lot of data on the Standard Out stream, then the time out message gets lost in the gobs of text so that it reads:

<TEXT>
Build timed out (after 3 minutes). Marked the build as aborted.
<TONS OF TEXT>
Build was aborted
Finished: ABORTED

In this event, it is not obvious to the users why the build was aborted since the "timed out" message is lost in the remaining standard out text. To add the confusion, if the user views the Jenkins error log to try to determine the cause for the abort, there is an "InterruptedException" that is raised that makes it appear as though Jenkins aborted the build due to an unexpected occurrence. Modifying the Finished message to say something like "Finished: TIMED OUT" would make it very clear to any user why the build stopped regardless of where the other time out message is displayed.
Also the exception in the Jenkins error log should be caught if it is an expected error, so that users are not left thinking Jenkins failed unexpectedly.

Errr log:
INFO: TEST #1 aborted
java.lang.InterruptedException
at java.lang.ProcessImpl.waitFor(Native Method)
at hudson.Proc$LocalProc.join(Proc.java:319)
at hudson.Launcher$ProcStarter.join(Launcher.java:336)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:82)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:693)
at hudson.model.Build$RunnerImpl.build(Build.java:178)
at hudson.model.Build$RunnerImpl.doRun(Build.java:139)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:459)
at hudson.model.Run.run(Run.java:1376)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:230)