Your corpus has far more diversity than mine... :)

I found only a very small handful of new exceptions aside from 59739, and those 
are probably caused by changes in Tika:

java.lang.IllegalArgumentException
        at 
org.apache.poi.openxml4j.opc.PackagingURIHelper.resolvePartUri(PackagingURIHelper.java:427)
        at 
org.apache.poi.openxml4j.opc.PackageRelationship.getTargetURI(PackageRelationship.java:206)
        at 
o.a.t.parser.microsoft.ooxml.XSSFExcelExtractorDecorator.addDrawingHyperLinks(XSSFExcelExtractorDecorator.java:174)

There are a few handfuls of files with markedly less content...I'll diagnose 
tomorrow.

-----Original Message-----
From: Dominik Stadler [mailto:[email protected]] 
Sent: Wednesday, June 22, 2016 3:23 PM
To: POI Developers List <[email protected]>
Subject: Re: 3.15 beta 2 soon?

Hi,

I did another run in the meantime with an intermediate fix for the 
HWPF-Version, see http://people.apache.org/~centic/poi_regression/reports/,
the following pops up now a few times:

java.lang.NullPointerException
        at 
o.a.p.xslf.usermodel.XSLFTextParagraph.getDefaultFontSize(XSLFTextParagraph.java:953)
        at 
o.a.p.sl.draw.DrawTextParagraph.getAttributedString(DrawTextParagraph.java:534)
        at o.a.p.sl.draw.DrawTextParagraph.breakText(DrawTextParagraph.java:235)
        at o.a.p.sl.draw.DrawTextShape.drawParagraphs(DrawTextShape.java:149)
        at o.a.p.sl.draw.DrawTextShape.getTextHeight(DrawTextShape.java:210)
        at o.a.p.sl.draw.DrawTextShape.drawContent(DrawTextShape.java:86)
        at o.a.p.sl.draw.DrawSimpleShape.draw(DrawSimpleShape.java:93)
        at o.a.p.sl.draw.DrawSheet.draw(DrawSheet.java:67)
        at o.a.p.sl.draw.DrawSlide.draw(DrawSlide.java:39)
        at o.a.p.xslf.usermodel.XSLFSlide.draw(XSLFSlide.java:301)
        at o.a.p.stress.SlideShowHandler.renderSlides(SlideShowHandler.java:120)
        at 
o.a.p.stress.SlideShowHandler.handleSlideShow(SlideShowHandler.java:43)
        at o.a.p.stress.XSLFFileHandler.handleFile(XSLFFileHandler.java:43)

and a few others once or twice, although I am not sure about those, some 
documents cause OOMs and these can cause concurrently running tests to run into 
timeouts and run through in the following run...

Dominik.


Reply via email to