[postgis-tickets] [PostGIS] #2190: topology regress failures on 9.3

[PostGIS]

#2190: topology regress failures on 9.3
----------------------+-----------------------------------------------------
 Reporter:  robe      |       Owner:  strk         
     Type:  defect    |      Status:  new          
 Priority:  blocker   |   Milestone:  PostGIS 2.1.0
Component:  topology  |     Version:  trunk        
 Keywords:            |  
----------------------+-----------------------------------------------------
 Debbie pulls the latest PostgreSQL 9.3 snapshot on Sunday and then does a
 regress and then tests with that for the rest of the week.  This Sunday
 she registered a topology regress failure:


 {{{
 PostgreSQL 9.3devel on x86_64-unknown-linux-gnu, compiled by gcc (Debian
 4.4.5-8) 4.4.5, 64-bit
   Postgis 2.1.0SVN - r11046 - 2013-01-28 06:06:36
   GEOS: 3.4.0dev-CAPI-1.8.0 r3755
   PROJ: Rel. 4.7.1, 23 September 2009

 Running tests

  regress/legacy_validate .. ok
  regress/legacy_predicate .. ok
  regress/legacy_invalid .. ok
  regress/sqlmm .. ok
  regress/legacy_query .. ok
  regress/addnode .. ok
  regress/addedge .. ok
  regress/addface .. ok
  regress/addface2.5d .. ok
  regress/addtopogeometrycolumn .. ok
  regress/polygonize .. ok
  regress/st_addisoedge .. ok
  regress/st_addisonode .. failed (diff expected obtained:
 /var/lib/jenkins/workspace/postgis/regress_pgdev/tmp/2_1_pg9.3w64/test_13_diff)
  regress/st_addedgemodface .. ok
  regress/st_addedgenewfaces .. ok
  regress/st_changeedgegeom .. ok
  regress/st_createtopogeo .. ok
  regress/st_getfacegeometry .. failed (diff expected obtained:
 /var/lib/jenkins/workspace/postgis/regress_pgdev/tmp/2_1_pg9.3w64/test_18_diff)
  regress/st_getfaceedges .. failed (diff expected obtained:
 /var/lib/jenkins/workspace/postgis/regress_pgdev/tmp/2_1_pg9.3w64/test_19_diff)
  regress/st_modedgeheal .. ok
  regress/st_modedgesplit .. failed (diff expected obtained:
 /var/lib/jenkins/workspace/postgis/regress_pgdev/tmp/2_1_pg9.3w64/test_21_diff)
  regress/st_newedgeheal .. ok
  regress/st_newedgessplit .. failed (diff expected obtained:
 /var/lib/jenkins/workspace/postgis/regress_pgdev/tmp/2_1_pg9.3w64/test_23_diff)
  regress/st_remedgenewface .. ok
  regress/st_remedgemodface .. ok
  regress/topoelement .. ok
  regress/topoelementarray_agg .. ok
  regress/topogeo_addlinestring .. ok
  regress/topogeo_addpoint .. ok
  regress/topogeo_addpolygon .. ok
  regress/topogeometry_type .. ok
  regress/topo2.5d .. ok
  regress/totopogeom .. ok
  regress/droptopology .. ok
  regress/copytopology .. ok
  regress/createtopogeom .. ok
  regress/createtopology .. ok
  regress/gml .. ok
  regress/getnodebypoint .. ok
  regress/getedgebypoint .. ok
  regress/getfacebypoint .. ok
  regress/getringedges .. ok
  regress/gettopogeomelements .. ok
  regress/layertrigger .. ok
  regress/validatetopology .. ok
  uninstall .. ok (4083)

 }}}

 Looks like they may have changed error handling

 -- addisonode - test_13_diff
 {{{
 11.OBT: ERROR:  SQL/MM Spatial exception - invalid topology name
 11.EXP: ERROR:  relation "wrong_name.node" does not exist at character 21
 }}}
 -- st_facegeometry -- test_18_diff

 {{{
 7.OBT: ERROR:  SQL/MM Spatial exception - invalid topology name
 7.EXP: ERROR:  corrupted topology "NonExistent"
 }}}
  -- st_faceedges -- test_19_diff

 {{{
 6.OBT: ERROR:  SQL/MM Spatial exception - invalid topology name
 6.EXP: ERROR:  relation "NonExistent.edge_data" does not exist at
 character 94
 }}}

 anyway I think you get the gist now.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2190>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.