High number of warnings causing Hudson to run out of heap space

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

High number of warnings causing Hudson to run out of heap space

Dale King-4

I added building of javadocs to a job for the first time and turned on parsing of javadoc warnings as well. There are lots of bad javadoc tags in the project so our number of warnings shot up from 200 to over 2000.

 

When viewing the compiler warnings from the compiler warnings plugin this number of warnings led to out of memory errors. Trying to view the warnings while a build was going actually caused the build to fail with an out of memory error.

 

2000 is a lot of warnings, but not so high that it should be crashing things.

 

Reply | Threaded
Open this post in threaded view
|

RE: High number of warnings causing Hudson to run out of heap space

Ulli Hafner-2
Hmm, that is strange. There are some problems if there are more then 25000 warnings but 2000 is not that much. Which memory options did you use for Hudson?
 
Ulli


From: Dale King [mailto:[hidden email]]
Sent: Thursday, July 02, 2009 8:40 PM
To: [hidden email]
Subject: High number of warnings causing Hudson to run out of heap space

I added building of javadocs to a job for the first time and turned on parsing of javadoc warnings as well. There are lots of bad javadoc tags in the project so our number of warnings shot up from 200 to over 2000.

 

When viewing the compiler warnings from the compiler warnings plugin this number of warnings led to out of memory errors. Trying to view the warnings while a build was going actually caused the build to fail with an out of memory error.

 

2000 is a lot of warnings, but not so high that it should be crashing things.