[gdal-dev] Why warp.py tests disabled?

Mateusz Loskot mateusz at loskot.net
Mon Aug 4 14:55:13 EDT 2008

Andrey Kiselev wrote:
> On Sat, Aug 02, 2008 at 03:20:59PM +0200, Mateusz Loskot wrote:
>> Could you tell me why some test cases of warp.py have been
>> disabled [1] ? The log message does not say much about.
>> http://trac.osgeo.org/gdal/changeset/14617
> Mateusz,
> These tests failed on some slaves (AFAIR on x86 hosts). I think it is
> due to the floating point issues, either computation errors or
> float-to-integer conversion. Actually I don't know what to do about
> that.


Thanks for the explanation. I have no idea either, so perhaps best
is to leave them disabled for now.

> Threshold is 1.0 for byte data type, so it means that we are
> having seriously different warping results on different hosts.

But do you consider these differences of warp_4 results
as effect of an error?

> At least these tests can be used locally when working with warping code.


Best regards,
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org

More information about the gdal-dev mailing list