Opened 11 years ago
Closed 11 years ago
#656 closed defect (fixed)
GeosisValidDetail mingw64-w32 gcc 4.5.4 POINT (1.#QNAN -5)
Reported by: | robe | Owned by: | strk |
---|---|---|---|
Priority: | major | Milestone: | 3.3.9 |
Component: | Default | Version: | 3.3.8 |
Severity: | Unassigned | Keywords: | |
Cc: |
Description
group: capi::GEOSisValidDetail, test: test<3> problem: assertion failed failed assertion: "Expected 'POINT (NAN -5)' or 'POINT (-1#IND -5)', Obtained 'POINT (1.#QNAN -5)"
I think this is a harmless error, but its preventing tests from continuing. This I'm seen in winnie's building of 3.3.9 (I need to set test for 3.4, 3.5)
I suspect it will be an error for 3.4. and 3.5 too.
Change History (7)
comment:1 by , 11 years ago
Version: | 3.4.0 → 3.3.8 |
---|
comment:2 by , 11 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:3 by , 11 years ago
comment:4 by , 11 years ago
yap that got past those tests geos_unit now she is complaining about the xmltester part
from threadtest.c:20: ../../include/geos/io/ByteOrderDataInStream.h:31:61: fatal error: iosfwd: No such file or directory compilation terminated. make[3]: *** [threadtest.o] Error 1 make[3]: Leaving directory `/c/jenkins/geos/branches/3.3/tests/thread' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/c/jenkins/geos/branches/3.3/tests/thread' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/c/jenkins/geos/branches/3.3/tests' make: *** [check-recursive] Error 1
I feel like we've solved this already maybe the fix has not been backported
comment:5 by , 11 years ago
It sounds like this is due to threadtest.c being a C file but needing C++ include dirs in the path. But threadtest.c on line 20 does not include ByteOrderDataInStream.h here. Can you show more of the message ?
PS: this is NOT xmltester, but test/thread (which is not really used / automatically run)
comment:6 by , 11 years ago
Beside, this ticket is about the ISNAN bug, use another for threadtest please. I will forward port the fix for this one.
comment:7 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Please try with r3909, in 3.3 branch (3.3.9) -- if it makes winnie happy I'll forward port to 3.4 and trunk