Opened 13 years ago

Closed 13 years ago

#761 closed defect (wontfix)

Raster: fail some check

Reported by: aperi2007 Owned by: pracine
Priority: medium Milestone: PostGIS 2.0.0
Component: raster Version: master
Keywords: Cc:

Description

Hi,

in the "make check" phase I see some error for raster section.

I'm using a postgres 9.0.2 on a debian 32 bit and the postgis 2.0.0 trunk last version.

I put log here.


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 -32768 WARNING: rt_band_set_nodata: NODATA value for 16BSI band got truncated from 32769 to -32768 WARNING: Pixel value for 16BSI band got truncated from -32769 to -32768 WARNING: Pixel value for 16BSI band got truncated from 32769 to -32768 ERROR: Coordinates out 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 out 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 out 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 out of range Testing 32BF band Testing 64BF band Testing band hasnodata flag ./testwkb

in hexwkb len: 122

out hexwkb len: 122

in hexwkb: 00000000003FF0000000000000400000000000000040080000000000004010000000000000401400000000000040180000000000000000000A00070008

out hexwkb: 0100000000000000000000F03F000000000000004000000000000008400000000000001040000000000000144000000000000018400A00000007000800

in hexwkb len: 128

out hexwkb len: 128

in hexwkb len: 138

out hexwkb len: 138

in hexwkb len: 152

out hexwkb len: 152

in hexwkb len: 152

out hexwkb len: 152 ext band path: /tmp/t.tif ext band num: 3

in hexwkb len: 152

out hexwkb len: 152

in hexwkb len: 284

out hexwkb len: 284

in hexwkb len: 284

out hexwkb len: 284

in hexwkb len: 284

out hexwkb len: 284

in hexwkb len: 284

out hexwkb len: 284

in hexwkb len: 284

out hexwkb len: 284 All tests successful ! make[3]: Leaving directory `/home/postgres/software/postgis/postgis-2.0.0SVN/raster/test/core' make[2]: Leaving directory `/home/postgres/software/postgis/postgis-2.0.0SVN/raster/test'

Consider also running make post-install-check after installation

make[1]: Leaving directory `/home/postgres/software/postgis/postgis-2.0.0SVN/raster'


Change History (2)

comment:1 by jorgearevalo, 13 years ago

If you're talking about the "ERROR: Coordinates out of range" messages, they're normal. And seems all the test have been successful.

comment:2 by aperi2007, 13 years ago

Resolution: wontfix
Status: newclosed

Hi Jorge, you are reason.

Sorry for noise.

Note: See TracTickets for help on using tickets.