The console output is interesting. There are two "runs" of the uimaj-core test suite.
- one run has 1 failure, looks like a bad test case in JCasHashMap, not a blocker to the release I think. - the 2nd run seems to be done because the Cobertura plugin is configured for this Jenkins build. This plugin measures code coverage, and (it seems) it re-runs the tests. This rerun has several additional errors - CasToInlineXmlTest - the SAX support there seems to not support formatted output - TestLog4jLogger_impl: the base logger doesn't have "INFO" set - perhaps on purpose - XMLSerializerTest: the attempt by the test to set xml version 1.1 didn't "take" These additional errors don't get counted by Jenkins - I guess they're a side effect of the way Cobertura runs. I'll post a Jira to improve the JCasHashMap test case to work on systems with different numbers of cores than the one I tested on :-) -Marshall On 5/1/2014 9:29 PM, Apache Jenkins Server wrote: > See <https://builds.apache.org/job/UIMA-SDK/521/changes> > > >
