Re: the toString compares in test cases The toString problems are fixed (I think :-) ), and I added a migration/compatibility flag, -Duima.v2_pretty_print_format which when provided, makes the pretty print format identical to v2 (subject to some "fixes" in v3 that have never been put into v2); this ought to make test cases which are comparing toString() results work.
As usual, any testing appreciated ! -Marshall On 9/29/2017 4:25 PM, Richard Eckart de Castilho wrote: >> On 28.09.2017, at 04:34, Marshall Schor <m...@schor.com> wrote: >> >> I reproduced this with more test case varieties - I added tests for all the >> varieties of serialization in CasIOUtils. >> >> While investigating this, I found another issue; both are now fixed. >> >> Richard, would be great if you could try again :-) > 6 down, 73 failures to go ;) > > Some of them are related to the change in the toString() format of feature > structures. > I'll fix these soon. > > However, some are still likely related to be issues in UIMAv3. For example, I > still get > an NPE when deserializing format 6 in lenient mode. > > java.lang.NullPointerException > at > org.apache.uima.cas.impl.BinaryCasSerDes6.deserializeAfterVersion(BinaryCasSerDes6.java:1839) > at > org.apache.uima.cas.impl.BinaryCasSerDes.reinit(BinaryCasSerDes.java:594) > ... > > Be invited to directly check the Jenkins logs [1] and/or trying to run the > respective DKPro Core > tests yourself. If not, I'll try to open new Jira's after I have fixed the > trivial failures and > once I have found the time to do some diagnosis on the non-trivial ones. > > Cheers, > > -- Richard > > P.S.: it's "DKPro Core" ;) > > [1] > https://zoidberg.ukp.informatik.tu-darmstadt.de/jenkins/job/DKPro%20Core%20(GitHub)%20-%20UIMAv3/lastBuild/testReport/ > >
