-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test failures with libspatialindex 2.0.0 #312
Comments
Thanks for the patch! I suppose we should just relax the version test or remote it entirely. It doesn't add too much at this point
Are you purposely building in Debug mode or is it accidentally being enabled? |
Answering my own question, |
libspatialindex/libspatialindex#246 addressed the extra debug noise here |
FWIW, it would be easier to write this as: self.assertTrue((index.major_version, index.minor_version) >= (1, 7)) and it would work for version 3 too. But removing the test makes more sense in this case. |
New libspatialindex beta available related to this https://github.com/libspatialindex/libspatialindex/releases/tag/2.0.0b2 |
No change with respect to the "Lost pointers" output with b2:
|
Hmph. Can you point me to where libspatialindex is being configured? I believe I had b2 set up so that if any Debug (RelWithDebInfo/Debug) is set as the CMAKE_BUILD_TYPE, it will output that stuff. Maybe it isn't worth the trouble at all I we should just drop it. Modern analysis tools can tell you all that stuff easily... |
The package builds on the Debian infrastructure haven't started yet at time of writing, this is my local build log: Note the use of |
New release should take care of this https://github.com/libspatialindex/libspatialindex/releases/tag/2.0.0b3 |
The Debian package build fails due to test failures when using spatialindex 2.0.0 from experimental:
This patch may suffice:
The text was updated successfully, but these errors were encountered: