...
[12:47:10 CST(-0600)] <dmccallum541> commented
[12:55:32 CST(-0600)] <JasonElwood> I'm finishing up the issue management and have another call from 2-3. the reports is next on the list for me
[17:24:54 CST(-0600)] <tbain> just thinking outloud When the build fails on the CI server the RAM usage gets extremely high - 588MBs out of 594 MBs, or only 6MBs left of RAM... right now at idle the CI server is using 361MBs/594MBs
[17:38:47 CST(-0600)] <JasonElwood> I noticed the same thing during my attempts. I shut down everything but Jenkins but it still failed at the same place. The one thing I didn't try it to set some maven_opts.
[18:32:34 CST(-0600)] <js701> Jason, I have checked in the changes. One thing of note, I have changed some inner joins to outer joins, this may result in your seeing data in the reports of interest. Also, still very curious as to why you don't see column headers. These are hard coded values and no way should they not be displayed if the report is generated.You might want to check the dates of your .jasper files.
[18:33:27 CST(-0600)] <js701> correction, I am checking in the changes. not done just yet.