I'm not a travis user, but with Jenkins there is an xunit plugin that opens up an api with test results for the specific build. since xunit formatting is standard/generic, we've implemented a parser that just gets the # of pass/failed tests and links to the build for further investigation.

We had a similar problem where posting all of the results was just more noise than useful, this is at least a good starting point for handling build result feedback.

We have methods to handle big build logs, and we have a backlog full of ideas on how to improve the way we handle big logs.

mocha -R min