Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#279 closed defect (fixed)

hausdorff regression test fails

Reported by: mloskot Owned by: pramsey
Priority: medium Milestone: PostGIS 1.5.0
Component: postgis Version: master
Keywords: hausdorff Cc:

Description (last modified by mloskot)

Running regression tests against PostGIS from current trunk (r4706) gives failure for the hausdorff test

hausdorff. failed (diff expected obtained: /tmp/pgis_reg_25454/test_44_diff)

and it looks it crashes the server

$ cat /tmp/pgis_reg_25454/test_44_diff
*** hausdorff_expected	2009-07-30 10:28:11.000000000 +0100
--- /tmp/pgis_reg_25454/test_44_out	2009-10-30 12:38:58.000000000 +0000
***************
*** 3,6 ****
  hausdorff_ls_ls_2|2
  hausdorff_ls_mp|1
  hausdorff_ls_ls_3|14.142135623731
! hausdorffdensify_ls_ls|70
--- 3,9 ----
  hausdorff_ls_ls_2|2
  hausdorff_ls_mp|1
  hausdorff_ls_ls_3|14.142135623731
! server closed the connection unexpectedly
! 	This probably means the server terminated abnormally
! 	before or while processing the request.
! connection to server was lost

I did full rebuild of both, PostGIS and GEOS.

Environment:

  • Linux 64-bit (Ubuntu 9.10 Karmic Koala)
  • GCC 4.4.1
  • GEOS (version 3.2.0 from SVN trunk 2710)
  • libxml2 2.7.5

Change History (5)

comment:1 by mloskot, 14 years ago

Description: modified (diff)

comment:2 by robe, 14 years ago

I wonder if this is related to #258 though Mark had fixed this and I believe he is running 64-bit so must have worked for him.

Can you check (ST_LineCrossingDirection) http://www.postgis.org/documentation/manual-svn/ST_LineCrossingDirection.html

Since that had similar issues too. I haven't tested against the latest GEOS trunk so that might be something else.

comment:3 by mloskot, 14 years ago

Description: modified (diff)

Updated info about my OS and libxml2

comment:4 by pramsey, 14 years ago

Resolution: fixed
Status: newclosed

Fixed in trunk at r4743.

comment:5 by mloskot, 14 years ago

Using recent r4749, I've confirmed the fix works well.

Thank you Paul!

Note: See TracTickets for help on using tickets.