Opened 9 years ago
Closed 9 years ago
#3477 closed defect (fixed)
topology regress failure on Winnie
Reported by: | robe | Owned by: | strk |
---|---|---|---|
Priority: | blocker | Milestone: | PostGIS 2.3.0 |
Component: | topology | Version: | master |
Keywords: | windows | Cc: |
Description
Okay this must have been something done in last couple of days. Unfotunately the tranuk of both Winnie and Debie were failing because of the sfcgal snaffu so I'm just seeing this issue now and it only seems to be on winnie.
PostgreSQL 9.5.1, compiled by Visual C++ build 1800, 32-bit Postgis 2.3.0dev - r14711 - 2016-02-27 08:06:33 scripts 2.3.0dev r14711 GEOS: 3.5.0-CAPI-1.9.0 r4090 PROJ: Rel. 4.9.1, 04 March 2015
regress/st_addedgemodface .. failed (diff expected obtained: /projects/postgis/tmp/2.3.0dev_pg9.5_geos3.5.0_gdal2.0.1w32/test_14_diff) ----------------------------------------------------------------------------- --- regress/st_addedgemodface_expected 2016-02-24 13:20:49 -0500 +++ /projects/postgis/tmp/2.3.0dev_pg9.5_geos3.5.0_gdal2.0.1w32/test_14_out 2016-02-27 03:11:04 -0500 @@ -168,7 +168,7 @@ T29|E34|55|9|35|16 T29|E55|-21|19|35|17 ERROR: Corrupted topology: adjacent edges 6 and -21 bind different face (1 and 0) -ERROR: Side-location conflict: new edge starts in face 1 and ends in face 0 +ERROR: Side-location conflict: new edge starts in face 64d and ends in face 64d F17|{3:17,3:35} F3,F4|{3:3,3:4,3:10,3:16,3:17,3:35} F5,N4|{1:4,3:5,3:11} -----------------------------------------------------------------------------
Seems to be that hideous PRiD64 formatting thing raring its head again.
Note:
See TracTickets
for help on using tickets.
(In [14713]) PRId64 to LWTFMT_ELEMID
Shoudl fix #3477