These failures have "gone away" this morning... A new svn checkout and build succeeded on the first try. I redid the uimaj-sdk build on Jenkins, and it now passed the RAT test OK at the end (it's sitting there, trying to deploy the result ... it might finish someday - not sure what the holdup is).
The addons build seems to still be getting out-of-permgen space errors - I found another field on the configuration table that sets MAVEN_OPTS so perhaps I was not setting it correctly. I changed the addons config on Jenkins to use the new field, and when the previous addons job "times out" I'll relaunch to see if that fixes things. The change to the Jenkins config: Before: add an "environment var" After: expand the Advanced under "Build" section - and there's a field labeled MAVEN_OPTS. I also changed the Java level to 1.5 (latest) (was 1.6 latest) - as we're supposed to run on 1.5 :-). -Marshall On 8/18/2011 5:40 PM, Marshall Schor wrote: > Just reporting this for now... > > A new checkout of the uimaj trunk, plus mvn install, seems to experience > intermittent failures in the docbook processing. Sometimes the docbook > processing generates "duplicate xml ids", which causes FOP to fail. > > Restarting the build after cleaning the project often then succeeds. > > The build on Jenkins failed at the very end- running RAT. I did a similar > checkout from trunk and after some restarts due to docbook failures, did not > get > a RAT failure. > > Sigh... -Marshall >
