buildbot success in ASF Buildbot on fop-trunk

[buildbot]

The Buildbot has detected a restored build on builder fop-trunk while building 
ASF Buildbot. Full details are available at:
http://ci.apache.org/builders/fop-trunk/builds/332

Buildbot URL: http://ci.apache.org/

Buildslave for this Build: orcus_ubuntu

Build Reason: The Nightly scheduler named 'fopNightly' triggered this build
Build Source Stamp: [branch xmlgraphics/fop/trunk] HEAD
Blamelist: 

Build succeeded!

Sincerely,
 -The Buildbot

Jenkins build is back to normal : xmlgraphics-commons #25

[Apache Jenkins Server]

See 

Build failed in Jenkins: xmlgraphics-commons #24

[Apache Jenkins Server]

See 

Changes:

[ssteiner] XGC-97: Add PreloaderRawPNG to handle images ImageIO cant

--
[...truncated 229 lines...]
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.079 sec
[junit] 
[junit] Testsuite: org.apache.xmlgraphics.image.loader.PenaltyTestCase
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.052 sec
[junit] 
[junit] Testsuite: 
org.apache.xmlgraphics.image.loader.PipelineFactoryTestCase
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.135 sec
[junit] 
[junit] Testsuite: 
org.apache.xmlgraphics.image.loader.cache.DefaultExpirationPolicyTestCase
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.059 sec
[junit] 
[junit] Testsuite: 
org.apache.xmlgraphics.image.loader.cache.ImageCacheTestCase
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 1.392 sec
[junit] 
[junit] Testsuite: 
org.apache.xmlgraphics.image.loader.impl.ImageLoaderFactoryPNGTestCase
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.081 sec
[junit] 
[junit] Testsuite: 
org.apache.xmlgraphics.image.loader.impl.ImageLoaderImageIOTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.346 sec
[junit] 
[junit] - Standard Error -
[junit] Jun 5, 2015 12:19:55 PM 
org.apache.xmlgraphics.image.loader.impl.imageio.ImageLoaderImageIO loadImage
[junit] WARNING: Image 
file:/x1/jenkins/jenkins-slave/workspace/xmlgraphics-commons/build/test-classes/org/apache/xmlgraphics/image/loader/impl/gray-vs-cmyk-profile.png
 has an incompatible color profile. The color profile will be ignored.
[junit] Color model of loaded bitmap: ColorModel: #pixelBits = 16 
numComponents = 2 color space = java.awt.color.ICC_ColorSpace@961dff 
transparency = 3 has alpha = true isAlphaPre = false
[junit] Color model of color profile: ColorModel: #pixelBits = 40 
numComponents = 5 color space = java.awt.color.ICC_ColorSpace@fcfa52 
transparency = 3 has alpha = true isAlphaPre = false
[junit] -  ---
[junit] Testsuite: 
org.apache.xmlgraphics.image.loader.impl.ImageLoaderPNGTestCase
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.232 sec
[junit] 
[junit] Testsuite: 
org.apache.xmlgraphics.image.loader.impl.ImageLoaderRawCCITTFaxTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.116 sec
[junit] 
[junit] Testsuite: 
org.apache.xmlgraphics.image.loader.impl.ImageLoaderRawPNGTestCase
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 1.262 sec
[junit] 
[junit] Testsuite: org.apache.xmlgraphics.image.loader.impl.PNGFileTestCase
[junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 0.187 sec
[junit] 
[junit] Testsuite: 
org.apache.xmlgraphics.image.loader.impl.PreloaderJPEGTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.172 sec
[junit] 
[junit] Testsuite: 
org.apache.xmlgraphics.image.writer.ImageWriterRegistryTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.058 sec
[junit] 
[junit] Testsuite: org.apache.xmlgraphics.image.writer.ResolutionTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.171 sec
[junit] 
[junit] - Standard Error -
[junit] Problem while writing image using ImageI/O: Metadata Adobe settings 
incompatible with image type. Metadata modified.
[junit] Problem while writing image using ImageI/O: Metadata Adobe settings 
incompatible with image type. Metadata modified.
[junit] -  ---
[junit] Testsuite: 
org.apache.xmlgraphics.image.writer.imageio.ImageIOTIFFImageWriterTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.051 sec
[junit] 
[junit] - Standard Output ---
[junit] Skipping endianness test for ImageIO-based TIFF writer because JAI 
ImageIO Tools is not available!
[junit] Skipping endianness test for ImageIO-based TIFF writer because JAI 
ImageIO Tools is not available!
[junit] -  ---
[junit] Testsuite: 
org.apache.xmlgraphics.io.TempResourceURIGeneratorTestCase
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.092 sec
[junit] 
[junit] Testsuite: org.apache.xmlgraphics.io.URIResolverAdapterTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.062 sec
[junit] 
[junit] Testsuite: org.apache.xmlgraphics.io.XmlSourceUtilTestCase
[junit] Tests run: 14, Failures: 0, Errors: 0, Time elapsed: 0.374 sec
[junit] 
[junit] Testsuite: org.apache.xmlgraphics.java2d.GraphicContextTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.094 sec
[junit] 

[jira] [Commented] (FOP-2481) AssertionError at BalancingColumnBreakingAlgorithm.getInitialBreaks

[Andreas L. Delmelle (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOP-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577690#comment-14577690
 ] 

Andreas L. Delmelle commented on FOP-2481:
--

Assertion was added in 
http://svn.apache.org/viewvc?diff_format=h&view=revision&revision=1419183. 
As it happens, none of the test cases added with said patch bothers to check 
the empty block / empty table condition... 
Almost like nobody sees these as valid use cases anymore. ;)

The par sequence in the call that fails consists of:
- a zero-width auxiliary box
- an infinite penalty
- a glue
- a forced break

Only the last element is a legal break, but the penalty's width is zero, so we 
never reach the point where anything gets added to initialColumns, which makes 
the assertion fail.

Not sure what the original intention was, but could be fixed in two ways:
- change the assertion to "initialColumns.size() <= ..."
- change the condition some 20 lines up from "breakLength > idealBreakLength" 
to "breakLength >= idealBreakLength"

My gut would go for the latter, and keep the assertion as is, but that's just 
me...

> AssertionError at BalancingColumnBreakingAlgorithm.getInitialBreaks
> ---
>
> Key: FOP-2481
> URL: https://issues.apache.org/jira/browse/FOP-2481
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
> Attachments: exception.fo
>
>
> AssertionError
>   at 
> org.apache.fop.layoutmgr.BalancingColumnBreakingAlgorithm.getInitialBreaks(BalancingColumnBreakingAlgorithm.java:171)
> export FOP_OPTS=-ea
> fop exception.fo out.pdf



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Change bars status

[Andreas Delmelle]

Hi Jan

> On 07 Jun 2015, at 19:39, Jan Tosovsky  wrote:

> I've found some progress on 'change bar' support here
> 
> https://issues.apache.org/jira/browse/FOP-1760
> 
> discussed further here:
> 
> http://apache-fop.1065347.n5.nabble.com/Change-bars-support-in-FOP-td38134.h
> tml
> 
> There is mentioned more test cases are required. What exactly should be
> tested? I could prepare something to help to move this feature forward.

I am unsure of the status of this patch, and how difficult it would be to apply 
it to the current trunk or the existing branch, but I can tell you that the 
tests that Glenn was referring to are mainly just a bunch of FO files. 
Preferably lots of them, exhaustively checking various scenarios.

In order to be easily usable as a "layout engine test", those FO files just 
need to be wrapped into a testcase document, with added assertions about the 
output. 

See: http://wiki.apache.org/xmlgraphics-fop/HowToCreateLayoutEngineTests

Note: this does require some affinity with the Area Tree XML format in order to 
get the XPath expressions for the checks correct, so if you do not have time to 
dive into that, it's OK to leave the checks node empty, or just write what you 
want to check in there as a comment (TODO).

If you already have the time and the patience to provide something resembling 
real-life use cases, that will be much appreciated. 

No guarantees about when someone will have time available to pick it up, 
though...


KR

Andreas