Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#2469 closed defect (fixed)

[raster]: travis raster regress failures

Reported by: robe Owned by: dustymugs
Priority: medium Milestone: PostGIS 2.0.4
Component: raster Version: 2.0.x
Keywords: Cc:

Description

Travis is failing regress on most of raster checks.

I think in my testing I've put at top

SET client_min_messages TO NOTICE;

But before I continue doing this, can we set some sort of global. For postgis I think we didn't because some we want a notice of WARNING because of differences with diffrent pgs.

I'm wondering if the test script can set it by default and allow overriding in the sql file.

HAve no clue how that works in postgis geometry or raster, but tht would be the ideal solution so I don't have to patch a ton of regress.sql files.

Change History (10)

comment:1 by robe, 11 years ago

latest build after patching a bunch of raster files. 13 someodd more to go

https://travis-ci.org/robe2/postgis/builds/10961024

Let me know if its not possible and I'll go ahead and patch the rest.

comment:2 by dustymugs, 11 years ago

It seems like NOTICEs that should be emitted are not in the output. Is the postgresql.conf set to a different client_min_messages setting?

comment:3 by robe, 11 years ago

Yes that's the problem but unfortunately we can't rely on people client_min_messages set a certain way and travis evidentally is set to something else in the 9.1 that comes packaged via ubuntu.

I'm not sure why travis PostgreSQL 9.1 is set that way but it is.

comment:4 by robe, 11 years ago

Summary: [raster: travis raster regress failures[raster]: travis raster regress failures

comment:5 by strk, 11 years ago

See if r11913 helps (thanks Mateusz)

comment:6 by dustymugs, 11 years ago

strk's change should work. I don't notice any changes on my machines.

comment:7 by robe, 11 years ago

Resolution: fixed
Status: newclosed

comment:8 by robe, 11 years ago

Milestone: PostGIS 2.1.1PostGIS 2.0.4

comment:9 by robe, 11 years ago

Fixed for 2.1.1 at r11925

comment:10 by robe, 11 years ago

fixed for 2.0 at r11926

Note: See TracTickets for help on using tickets.