[Geoserver-devel] Travis hates our verbose builds

GeoServer GeoServer Developer
1

Hi,
this morning I made the build go a bit further with JDK 7 and Travis welcomed my efforts with the following error message:

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

Erk… seems a bit extreme, but hey, it’s given for free.
And indeed looking at a GeoServer build scroll by makes it difficult to see if things are going ok or not.
Besides tests printing on the standard output (normally, leftovers), the build is really logging a ton of exceptions… and it does because
we are indeed testing a number of exceptional conditions that should raise them.

Now, those are not really errors, it’s us testing that GeoServer responds to invalid requests with a service exception most of the time.
So, how about we turn down the build logging so that not even error messages are logged?
The build already sets up the the quietTests system variable to true, so that we run with the QUIET_LOGGING.properties profile,
something that is not up when running tests in the IDE, where the profile is instead TEST_LOGGING.properties.

So, I guess the proposal is, can we switch QUIET_LOGGING to use:

log4j.rootLogger=OFF, stdout

instead?

I’ve built geoserver with just a single thread and dumped the output to a file so that you can see how it looks:
https://dl.dropboxusercontent.com/u/2361103/build.log.gz

Unpacked it’s still 1.8MB, mostly due to a number of tests that do output large xml files for debugging purposes, we
might want to have a look at those and do some clean up.
As said, this would be only the output from maven, if you run tests from the IDE it would used TEST_LOGGING instead
and all exceptions would be logged as usual.

Opinions?

Cheers
Andrea

–

==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

2

On Sat, Oct 5, 2013 at 6:53 AM, Andrea Aime <andrea.aime@anonymised.com>wrote:

Hi,
this morning I made the build go a bit further with JDK 7 and Travis
welcomed my efforts with the following error message:

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

Erk... seems a bit extreme, but hey, it's given for free.
And indeed looking at a GeoServer build scroll by makes it difficult to
see if things are going ok or not.
Besides tests printing on the standard output (normally, leftovers), the
build is really logging a ton of exceptions... and it does because
we are indeed testing a number of exceptional conditions that should raise
them.

Now, those are not really errors, it's us testing that GeoServer responds
to invalid requests with a service exception most of the time.
So, how about we turn down the build logging so that not even error
messages are logged?
The build already sets up the the quietTests system variable to true, so
that we run with the QUIET_LOGGING.properties profile,
something that is not up when running tests in the IDE, where the profile
is instead TEST_LOGGING.properties.

So, I guess the proposal is, can we switch QUIET_LOGGING to use:

log4j.rootLogger=OFF, stdout

instead?

+1

I've built geoserver with just a single thread and dumped the output to a
file so that you can see how it looks:
https://dl.dropboxusercontent.com/u/2361103/build.log.gz

Unpacked it's still 1.8MB, mostly due to a number of tests that do output
large xml files for debugging purposes, we
might want to have a look at those and do some clean up.

Agreed.

As said, this would be only the output from maven, if you run tests from
the IDE it would used TEST_LOGGING instead
and all exceptions would be logged as usual.

Opinions?

All sounds good to me. Thanks for all the work setting up travis.

Cheers
Andrea

--

Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
*Justin Deoliveira*
Vice President, Engineering | Boundless
jdeolive@anonymised.com
@j_deolive <https://twitter.com/j_deolive&gt;