[Geoserver-devel] wcs 2.0 build failure on master

Digging into build failures on master …

Failed tests: testScaleToSizeXML(org.geoserver.wcs2_0.xml.ScalingExtentionTest): expected:<[image/tiff]> but was:<[application/xml]>

So I am going to guess a nested exception, looking at ares surefire test results:

Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 13.563 sec <<< FAILURE!
testScaleToSizeXML(org.geoserver.wcs2_0.xml.ScalingExtentionTest) Time elapsed: 4605 sec <<< FAILURE!
junit.framework.ComparisonFailure: expected:<[image/tiff]> but was:<[application/xml]>
at junit.framework.Assert.assertEquals(Assert.java:100)
at junit.framework.Assert.assertEquals(Assert.java:107)
at junit.framework.TestCase.assertEquals(TestCase.java:269)
at org.geoserver.wcs2_0.xml.ScalingExtentionTest.testScaleToSizeXML(ScalingExtentionTest.java:78)

So not much help, I will reproduce locally and report back. I wonder if there is a good way to report service exceptions consistently in our logs to aid in debugging.

···


Jody Garnett

Was unable to reproduce locally (i.e. build succeeded).

Not sure what is up, asking ares to try again - and it also succeeded.

···

On 11 August 2015 at 12:04, Jody Garnett <jody.garnett@anonymised.com> wrote:

Digging into build failures on master …

Failed tests: testScaleToSizeXML(org.geoserver.wcs2_0.xml.ScalingExtentionTest): expected:<[image/tiff]> but was:<[application/xml]>

So I am going to guess a nested exception, looking at ares surefire test results:

Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 13.563 sec <<< FAILURE!
testScaleToSizeXML(org.geoserver.wcs2_0.xml.ScalingExtentionTest) Time elapsed: 4605 sec <<< FAILURE!
junit.framework.ComparisonFailure: expected:<[image/tiff]> but was:<[application/xml]>
at junit.framework.Assert.assertEquals(Assert.java:100)
at junit.framework.Assert.assertEquals(Assert.java:107)
at junit.framework.TestCase.assertEquals(TestCase.java:269)
at org.geoserver.wcs2_0.xml.ScalingExtentionTest.testScaleToSizeXML(ScalingExtentionTest.java:78)

So not much help, I will reproduce locally and report back. I wonder if there is a good way to report service exceptions consistently in our logs to aid in debugging.


Jody Garnett


Jody Garnett