Stanbol Build output

[Reto Gmür <re...@wymiwyg.com>]

Hello,

I just tried to build Stanbol on travis-ci.

Unfortunately the build ends with:


The log length has exceeded the limit of 4 Megabytes (this usually means
that test suite is raising the same exception over and over).

The build has been terminated.


See: https://s3.amazonaws.com/archive.travis-ci.org/jobs/26118135/log.txt

I think that having such a long log from the tests isn't very useful. What
do you think, should a passing test be quiet? or how much output do you
think is reasonable?

Cheers,
Reto

Re: Stanbol Build output

[Rupert Westenthaler <ru...@gmail.com>]

Hi Reto,

* you can search for log4j config files in test/resources folders and
change levels from DEBUG to INFO
* you can set org.apache.solr.* loggers to ERROR in the same files.

this should reduce the size of the logs during a build enough to stay
under the limit.

best
Rupert

On Tue, May 27, 2014 at 2:00 PM, Reto Gmür <re...@wymiwyg.com> wrote:
> Hello,
>
> I just tried to build Stanbol on travis-ci.
>
> Unfortunately the build ends with:
>
>
> The log length has exceeded the limit of 4 Megabytes (this usually means
> that test suite is raising the same exception over and over).
>
> The build has been terminated.
>
>
> See: https://s3.amazonaws.com/archive.travis-ci.org/jobs/26118135/log.txt
>
> I think that having such a long log from the tests isn't very useful. What
> do you think, should a passing test be quiet? or how much output do you
> think is reasonable?
>
> Cheers,
> Reto



-- 
| Rupert Westenthaler             rupert.westenthaler@gmail.com
| Bodenlehenstraße 11                              ++43-699-11108907
| A-5500 Bischofshofen
| REDLINK.CO ..........................................................................
| http://redlink.co/