[Geoserver-devel] default output strategy == SPEED?

Hi all,

I am a loss to explain why but when i ran the cite tests on built artifacts for 2.1-beta1 I ran into some issues with some tests failing. And I have been running the same tests all week and the same tests did not fail. The issue occurs due to the output strategy of speed being used, and the test case test an exception case.

By definition with speed this is not meant to work as with that output strategy output gets written immediately, so when the exception report is written the result is an invalid document.

Looking at svn history it seems SPEED has been the default for quite some time. I am puzzled, I am not sure how tests have been passing recently… and what made it all of a sudden start failing. And I don’t see any recent changes that could have caused this change.

Any thoughts?

-Justin


Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

Justin Deoliveira ha scritto:

Hi all,

I am a loss to explain why but when i ran the cite tests on built artifacts for 2.1-beta1 I ran into some issues with some tests failing. And I have been running the same tests all week and the same tests did not fail. The issue occurs due to the output strategy of speed being used, and the test case test an exception case.

By definition with speed this is not meant to work as with that output strategy output gets written immediately, so when the exception report is written the result is an invalid document.

Looking at svn history it seems SPEED has been the default for quite some time. I am puzzled, I am not sure how tests have been passing recently... and what made it all of a sudden start failing. And I don't see any recent changes that could have caused this change.

Any thoughts?

I have no idea of what could have caused that. However we can just
go back to the partial buffer strategy, should be good out of the box

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

Ok, I will drop us back to partial buffer.

On Fri, Sep 3, 2010 at 2:58 AM, Andrea Aime <aaime@anonymised.com> wrote:

Justin Deoliveira ha scritto:

Hi all,

I am a loss to explain why but when i ran the cite tests on built artifacts for 2.1-beta1 I ran into some issues with some tests failing. And I have been running the same tests all week and the same tests did not fail. The issue occurs due to the output strategy of speed being used, and the test case test an exception case.

By definition with speed this is not meant to work as with that output strategy output gets written immediately, so when the exception report is written the result is an invalid document.

Looking at svn history it seems SPEED has been the default for quite some time. I am puzzled, I am not sure how tests have been passing recently… and what made it all of a sudden start failing. And I don’t see any recent changes that could have caused this change.

Any thoughts?

I have no idea of what could have caused that. However we can just
go back to the partial buffer strategy, should be good out of the box

Cheers
Andrea


Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.


Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.