You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@pdfbox.apache.org by Orion Poplawski <or...@cora.nwra.com> on 2014/06/18 06:34:11 UTC
Re:Disabling TestImageIOUtils
On 05/16/2014 03:53 AM, Andreas Lehmkühler wrote:
> Hi,
>
>
>> Orion Poplawski <or...@cora.nwra.com> hat am 8. Mai 2014 um 05:17 geschrieben:
>>
>>
>> On 05/02/2014 10:26 AM, Andreas Lehmkuehler wrote:
>>> The Apache PDFBox community is pleased to announce the release of
>>> Apache PDFBox version 1.8.5. The release is available for download at:
>>>
>>> http://pdfbox.apache.org/downloads.html
>>
>> This release presents something of a challenge for the Fedora package.
>> First off I will need to disable access to
>> com.levigo.jbig2:levigo-jbig2-imageio and possibly
>> net.java.dev.jai-imageio:jai-imageio-core-standalone in pdfbox.
>>
>> But then I get test failures:
>>
>> Tests run: 139, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 9.121
>> sec <<< FAILURE! - in org.apache.pdfbox.TestAll
>> testRenderImage(org.apache.pdfbox.util.TestImageIOUtils) Time elapsed:
>> 1.238 sec <<< FAILURE!
>> junit.framework.AssertionFailedError: X resolution doesn't match in
>> image file target/test-output/raw_image_demo.pdf-1.bmp expected:<120>
>> but was:<0>
>> at junit.framework.Assert.fail(Assert.java:57)
>> at junit.framework.Assert.failNotEquals(Assert.java:329)
>> at junit.framework.Assert.assertEquals(Assert.java:78)
>> at junit.framework.Assert.assertEquals(Assert.java:234)
>> at junit.framework.TestCase.assertEquals(TestCase.java:401)
>> at
>> org.apache.pdfbox.util.TestImageIOUtils.checkBmpResolution(TestImageIOUtils.java:352)
>> at
>> org.apache.pdfbox.util.TestImageIOUtils.checkResolution(TestImageIOUtils.java:300)
>> at
>> org.apache.pdfbox.util.TestImageIOUtils.doTestFile(TestImageIOUtils.java:135)
>> at
>> org.apache.pdfbox.util.TestImageIOUtils.testRenderImage(TestImageIOUtils.java:278)
>>
>>
>> Results :
>>
>> Failed tests:
>>
>> TestImageIOUtils.testRenderImage:278->doTestFile:135->checkResolution:300->checkBmpResolution:352
>> X resolution doesn't match in image file
>> target/test-output/raw_image_demo.pdf-1.bmp expected:<120> but was:<0>
>>
>> I'd like to not have to disable all tests in the build. Could there be
>> some way to completely disable this functionality?
> Maybe we should implement an optional switch to disable that part of the test if
> necessary.
>
> @Orion: Is that a possible solution you can live with?
>
> BR
> Andreas Lehmkühler
I don't see the pom entries on trunk, can this change be made there too?
Thanks,
Orion
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion@cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
Re: Disabling TestImageIOUtils
Posted by Tilman Hausherr <TH...@t-online.de>.
Am 18.06.2014 06:34, schrieb Orion Poplawski:
> On 05/16/2014 03:53 AM, Andreas Lehmkühler wrote:
>> Hi,
>>
>>
>>> Orion Poplawski <or...@cora.nwra.com> hat am 8. Mai 2014 um 05:17 geschrieben:
>>>
>>>
>>> On 05/02/2014 10:26 AM, Andreas Lehmkuehler wrote:
>>>> The Apache PDFBox community is pleased to announce the release of
>>>> Apache PDFBox version 1.8.5. The release is available for download at:
>>>>
>>>> http://pdfbox.apache.org/downloads.html
>>> This release presents something of a challenge for the Fedora package.
>>> First off I will need to disable access to
>>> com.levigo.jbig2:levigo-jbig2-imageio and possibly
>>> net.java.dev.jai-imageio:jai-imageio-core-standalone in pdfbox.
>>>
>>> But then I get test failures:
>>>
>>> Tests run: 139, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 9.121
>>> sec <<< FAILURE! - in org.apache.pdfbox.TestAll
>>> testRenderImage(org.apache.pdfbox.util.TestImageIOUtils) Time elapsed:
>>> 1.238 sec <<< FAILURE!
>>> junit.framework.AssertionFailedError: X resolution doesn't match in
>>> image file target/test-output/raw_image_demo.pdf-1.bmp expected:<120>
>>> but was:<0>
>>> at junit.framework.Assert.fail(Assert.java:57)
>>> at junit.framework.Assert.failNotEquals(Assert.java:329)
>>> at junit.framework.Assert.assertEquals(Assert.java:78)
>>> at junit.framework.Assert.assertEquals(Assert.java:234)
>>> at junit.framework.TestCase.assertEquals(TestCase.java:401)
>>> at
>>> org.apache.pdfbox.util.TestImageIOUtils.checkBmpResolution(TestImageIOUtils.java:352)
>>> at
>>> org.apache.pdfbox.util.TestImageIOUtils.checkResolution(TestImageIOUtils.java:300)
>>> at
>>> org.apache.pdfbox.util.TestImageIOUtils.doTestFile(TestImageIOUtils.java:135)
>>> at
>>> org.apache.pdfbox.util.TestImageIOUtils.testRenderImage(TestImageIOUtils.java:278)
>>>
>>>
>>> Results :
>>>
>>> Failed tests:
>>>
>>> TestImageIOUtils.testRenderImage:278->doTestFile:135->checkResolution:300->checkBmpResolution:352
>>> X resolution doesn't match in image file
>>> target/test-output/raw_image_demo.pdf-1.bmp expected:<120> but was:<0>
>>>
>>> I'd like to not have to disable all tests in the build. Could there be
>>> some way to completely disable this functionality?
>> Maybe we should implement an optional switch to disable that part of the test if
>> necessary.
>>
>> @Orion: Is that a possible solution you can live with?
>>
>> BR
>> Andreas Lehmkühler
> I don't see the pom entries on trunk, can this change be made there too?
The trunk build works differently, you would have to add that test to
the "exclude" list.
Tilman
>
> Thanks,
>
> Orion
>