copytopology regress on 9.2rc1 windows 32

[robe]

could be something with my config though rest seems to work fine. I'm getting a regress on copy topology on my 9.2rc1 x32 windows bot.

25.OBT: layer_id_seq|1|1|1|9223372036854775807|1|1|1|f|f
25.EXP: layer_id_seq|1|1|1|9223372036854775807|1|1|0|f|f

PostgreSQL 9.2rc1 on i686-w64-mingw32, compiled by i686-w64-mingw32-gcc.exe (GCC) 4.5.4 20111030 (prerelease) [svn/rev.180676 - mingw-w64/oz], 32-bit
  Postgis 2.1.0SVN
 - r10206
 - 2012-08-28 17:51:39
  GEOS: 3.4.0dev-CAPI-1.8.0 r0
  PROJ: Rel. 4.8.0, 6 March 2012

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 .. ok 
 regress/st_addedgemodface .. ok 
 regress/st_addedgenewfaces .. ok 
 regress/st_changeedgegeom .. ok 
 regress/st_createtopogeo .. ok 
 regress/st_getfacegeometry .. ok 
 regress/st_getfaceedges .. ok 
 regress/st_modedgeheal .. ok 
 regress/st_modedgesplit .. ok 
 regress/st_newedgeheal .. ok 
 regress/st_newedgessplit .. ok 
 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 .. failed (diff expected obtained: /tmp/pgis_reg/test_35_diff)
 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 (4061
)

Run tests: 46
Failed: 1

confgure details:

 PostGIS is now configured for i686-w64-mingw32

 -------------- Compiler Info ------------- 
  C compiler:           i686-w64-mingw32-gcc -g -O2
  C++ compiler:         i686-w64-mingw32-g++ -g -O2
  SQL preprocessor:     /mingw/bin/cpp -traditional-cpp -P

 -------------- Dependencies -------------- 
  GEOS config:          /c/jenkins/geos/rel-3.4.0devw32/bin/geos-config
  GEOS version:         3.4.0dev
  GDAL config:          /c/jenkins/gdal/rel-1.9.1w32/bin/gdal-config
  GDAL version:         1.9.1
  PostgreSQL config:    /c/jenkins/postgresql/rel/pg9.2rc1w32/bin/pg_config
  PostgreSQL version:   PostgreSQL 9.2rc1
  PROJ4 version:        48
  Libxml2 config:       /c/ming32/projects/libxml/rel-libxml2-2.7.8w32/bin/xml2-config
  Libxml2 version:      2.7.8
  JSON-C support:       yes
  PostGIS debug level:  0
  Perl:                 /bin/perl

 --------------- Extensions --------------- 
  PostGIS Raster:       enabled
  PostGIS Topology:     enabled

 -------- Documentation Generation -------- 
  xsltproc:             /c/ming32/projects/xsltproc/xsltproc
  xsl style sheets:     /c/ming32/projects/docbook/docbook-xsl-1.76.1
  dblatex:              
  convert:              /c/Windows/system32/convert
  mathml2.dtd:          http://www.w3.org/Math/DTD/mathml2/mathml2.dtd

I thought someone had a similar issue on user group, but can't find that note.

[robe]

same error on my 9.2 64-bit rc1 though the beta2s I've been testing with in the past were fine.

[robe]

strk -- I think this is probably an issue with all 9.2 that log_cnt is not returning what old versions did. I found this:

​http://postgresql.1045698.n5.nabble.com/pgsql-Don-t-select-log-cnt-in-sequence-regression-tests-td4514085.html

I wonder if we should do the same, change your SELECT * calls well at least for the

SELECT * from "CITY_data_UP_down".layer_id_seq;

to

SELECT sequence_name, last_value, start_value, increment_by, max_value, min_value, cache_value, is_cycled, is_called from "CITY_data_UP_down".layer_id_seq;

[strk]

We surely don't care about the gory details of the sequence, just want to check the current value (what you'd get by nextval). The name would likely be useful for a context, but nothing more than that. Feel free to change the query to restrict selected items.

[robe]

fixed enough to pass 9.2rc1 regress at r10234

[strk]

Could you please backport to 2.0 branch ? Also PostgreSQL-9.1 on Ubuntu 12.04 is affected

[strk]

Well, I did: r10248 for 2.0 branch

[strk]

Reopening: the testcase was correct, it's CopyTopology still bogus when it comes to 9.1. See #2080

[strk]

ok forget this, the log_cnt is unrelated to that problem. At least I think...