gildegoma/salat — comment on commit 08b51357ca8c32dc151a0dd93d8f2cee6ece3da0
File:  line 0
By gildegoma:

Hi Michael! Thank you for the feedback and very sorry for the troubles caused... I noticed yesterday that something was going wrong, but unfortunately I had no time left to report the problem to IRC channel. I updated to master branch and did not paid attention to salat build output, but it's huge: 225MB and 1'476'439 DEBUG lines (not always, see previous build http://travis-ci.org/#!/gildegoma/salat/builds/370563)! That was not fair at all! I hope it was not big problem to identify and recover from.

I have therefore some questions and remarks (if you have time and will):

* Should (or Could) you hack in Travis database to mark this faulty build as 'finished' ? Build Nr 4 is always marked in yellow (running for more 23 hours now!) see http://travis-ci.org/#!/gildegoma/salat/builds. If not marked as finished, would it impact further builds run (5,6,...) ?
* Same JVM tuning (taken from examples like [Play20](http://travis-ci.org/#!/gildegoma/Play20/builds/475049) local sbt and https://github.com/paulp/sbt-extras) for sbt-lauch.jar works fine to avoid Java StackOverflow errors (see successful builds for [Akka](http://travis-ci.org/#!/gildegoma/akka/builds/474946) or [Scalatra](http://travis-ci.org/#!/gildegoma/scalatra/builds/475150)) --> **.deb package in the sbt travis-cookbook should be changed in this way...**. I'll try to fix it soon and open a pull request in this way...

Anyway, sorry again and many thanks for the error report + details. Next time, I will double-check my local output size before pushing changes up.