So, try # 1 was assigned "Windows2" - a different Windows machine than used before (in build 586). That build didn't even get started - while Jenkins was parsing the maven poms, it threw a fatal "out of permgen space". It sounds like the Java level installed on that machine has some configuration issues.
I restarted it, and it is assigned now to Windows1... -Marshall On 11/5/2014 10:25 AM, Marshall Schor wrote: > I added some debug output to record the JVM name and the specified name of the > TransformerFactory (if any). > > I reran on Jenkins, and Jenkins picked the Ubuntu slave (failure was on > Windows1) and I watched the console - no error reported on the xml tests. > > I've temporarily restricted the build for UIMA-SDK to "Windows" to see if I > can > reproduce this failure. > > -Marshall > > On 11/4/2014 4:43 PM, Marshall Schor wrote: >> Hi, >> >> I was watching the console log for UIMA-SDK #586, and noticed it said along >> the >> way some failure indications, for instance: >> >> testCAStoString(org.apache.uima.util.CasToInlineXmlTest) Time elapsed: 0.027 >> sec <<< FAILURE! >> >> So, I was quite surprised when the build finished and sent email to this list >> saying everything was successful. >> >> Going to Jenkins test report for build # 586 here: >> https://builds.apache.org/job/UIMA-SDK/org.apache.uima$uimaj-core/586/testReport/ >> says >> there are no errors. >> >> But looking at the console output >> https://builds.apache.org/view/All/job/UIMA-SDK/586/console definitely shows >> errors. >> >> (The errors seem to be due to different XML formatters; one writing <xxx >> .... >> /> and the other <xxx .... ></xxx>. Richard pointed me to a utility to get >> around this, and I can add that, so these won't fail.) >> >> But more importantly, does anyone have any idea why one part of Jenkins (the >> console log) is reporting failures, and the other part (test summary) is >> saying >> there are no failures? >> >> -M >> >> > >
