[postgis-devel] [wktraster] Core tests failure for r5841

[Pierre Racine]

Probably my fault. Double check...

Pierre

>-----Original Message-----
>From: postgis-devel-bounces at postgis.refractions.net [mailto:postgis-devel-
>bounces at postgis.refractions.net] On Behalf Of Jorge Arévalo
>Sent: 23 août 2010 07:39
>To: PostGIS Development Discussion
>Subject: Re: [postgis-devel] [wktraster] Core tests failure for r5841
>
>On Mon, Aug 23, 2010 at 1:04 PM, Mateusz Loskot <mateusz at loskot.net> wrote:
>> Hi,
>>
>> I've noticed current revision of WKT Raster is broken.
>> Running the core tests for r5841 ends up with assertion and
>> load of warnings:
>>
>> ./testapi
>> 1111 pixtype = 2
>> Raster starts with 0 bands
>> First point on convexhull ring is 0.5,0.5
>> Second point on convexhull ring is 256.5,1280.5
>> Third point on convexhull ring is 1280.5,1536.5
>> Fourth point on convexhull ring is 1024.5,256.5
>> Fifth point on convexhull ring is 0.5,0.5
>> Testing polygonize function
>> Testing 1BB band
>> WARNING: rt_band_set_nodata: NODATA value for 1BB band got truncated from 2
>> to 0
>> WARNING: rt_band_set_nodata: NODATA value for 1BB band got truncated from 3
>> to 1
>> WARNING: Pixel value for 1BB band got truncated from 2 to 0
>> WARNING: Pixel value for 1BB band got truncated from 3 to 1
>> Testing 2BB band
>> WARNING: rt_band_set_nodata: NODATA value for 2BUI band got truncated from 4
>> to 0
>> WARNING: rt_band_set_nodata: NODATA value for 2BUI band got truncated from 5
>> to 1
>> WARNING: Pixel value for 2BUI band got truncated from 4 to 0
>> WARNING: Pixel value for 2BUI band got truncated from 5 to 1
>> Testing 4BUI band
>> WARNING: rt_band_set_nodata: NODATA value for 4BUI band got truncated from
>> 16 to 0
>> WARNING: rt_band_set_nodata: NODATA value for 4BUI band got truncated from
>> 17 to 1
>> WARNING: Pixel value for 4BUI band got truncated from 35 to 3
>> Testing 8BUI band
>> WARNING: rt_band_set_nodata: NODATA value for 8BUI band got truncated from
>> 256 to 0
>> WARNING: Pixel value for 8BUI band got truncated from 256 to 0
>> Testing 8BSI band
>> WARNING: rt_band_set_nodata: NODATA value for 8BSI band got truncated from
>> -129 to 127
>> WARNING: rt_band_set_nodata: NODATA value for 8BSI band got truncated from
>> 129 to -127
>> WARNING: Pixel value for 8BSI band got truncated from -129 to 127
>> WARNING: Pixel value for 8BSI band got truncated from 129 to -127
>> Testing 16BSI band
>> WARNING: rt_band_set_nodata: NODATA value for 16BSI band got truncated from
>> -32769 to 32767
>> WARNING: rt_band_set_nodata: NODATA value for 16BSI band got truncated from
>> 32769 to -32767
>> WARNING: Pixel value for 16BSI band got truncated from -32769 to 32767
>> WARNING: Pixel value for 16BSI band got truncated from 32769 to -32767
>> ERROR: Coordinates ouf of range
>> Testing 16BUI band
>> WARNING: rt_band_set_nodata: NODATA value for 16BUI band got truncated from
>> 65536 to 0
>> WARNING: Pixel value for 16BUI band got truncated from 65536 to 0
>> ERROR: Coordinates ouf of range
>> Testing 32BUI band
>> WARNING: rt_band_set_nodata: NODATA value for 32BUI band got truncated from
>> 4.29497e+09 to 0
>> WARNING: Pixel value for 32BUI band got truncated from 4.29497e+09 to 0
>> ERROR: Coordinates ouf of range
>> Testing 32BSI band
>> WARNING: rt_band_set_nodata: NODATA value for 32BSI band got truncated from
>> 2.14748e+09 to -2.14748e+09
>> WARNING: Pixel value for 32BSI band got truncated from 2.14748e+09 to
>> -2.14748e+09
>> ERROR: Coordinates ouf of range
>> Testing 32BF band
>> Testing 64BF band
>> Testing band hasnodata flag
>> testapi: rt_api.c:545: rt_band_get_data: Assertion `((void *)0) != band'
>> failed.
>> make[2]: *** [check] Aborted
>> make[2]: Leaving directory
>> `/home/mloskot/dev/wktraster/_svn/trunk/test/core'
>> make[1]: *** [check] Error 2
>> make[1]: Leaving directory `/home/mloskot/dev/wktraster/_svn/trunk/test'
>> make: *** [check] Error 2
>>
>> The assertion is serious and happens in crucial function.
>> I checked and the last healthy revision seems to be r5811.
>>
>> Pierre, Jorge, could you re-validate your recent commits?
>> You do run "make check" before every commit, don't you?
>>
>> Best regards,
>> --
>> Mateusz Loskot, http://mateusz.loskot.net
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at postgis.refractions.net
>> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>>
>
>The problem seems to be in the 1BB band of the testing raster. Working
>on it... And yes, I always do make check before commit, but I'll check
>my commits again :-)
>
>Best regards,
>
>--
>Jorge Arévalo
>DEIMOS Space
>Internet & Mobilty Division
>Ronda de Poniente 19. Edificio Fiteni VI, portal 2, 2º
>28760 Tres Cantos (Madrid)
>Tel: +34 91 806 34 50 - ext: 155
>jorge.arevalo at deimos-space.com
>http://gis4free.wordpress.com
>_______________________________________________
>postgis-devel mailing list
>postgis-devel at postgis.refractions.net
>http://postgis.refractions.net/mailman/listinfo/postgis-devel