Skip to content
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

Regression test doesn't cover flat-nodes #186

Closed
pnorman opened this issue Sep 25, 2014 · 4 comments
Closed

Regression test doesn't cover flat-nodes #186

pnorman opened this issue Sep 25, 2014 · 4 comments

Comments

@pnorman
Copy link
Collaborator

pnorman commented Sep 25, 2014

The Liechtenstein extract is ill-suited for this, but we have no test coverage of flat nodes.

One potential issue specific to flat-nodes is that it's a file and it could have different behavior if there's a previous flat nodes file with the same name.

@alex85k
Copy link
Contributor

alex85k commented Sep 26, 2014

And also the flat-nodes test will be very slow on most machines...

By the way, current default max ID is > 3000000000 and default reserved space is 1.5 times smaller.

@pnorman
Copy link
Collaborator Author

pnorman commented Sep 26, 2014

Flat nodes is not particularly slow, even on one of my more normal machines.

@apmon
Copy link
Contributor

apmon commented Sep 26, 2014

flat nodes is probably a case where you want to do unit testing rather than integration testing. That way you need to write much less of the file than you would even if you import just liechtenstein.

node-persistent-cache-reader.c has some (primitive) stand alone code to test/benchmark some aspects of the flat nodes sub system. One could presumably expand that to do some proper unit testing of the likely things that could (or have) gone wrong with the flat nodes system. You will still need ~20GB of space to hold the flat node file. But you presumably don't have to write to all of it, and so if you have a modern filesystem that can create a large (sparse) file quickly, tests shouldn't be too bad.

@pnorman
Copy link
Collaborator Author

pnorman commented Sep 26, 2014

Yes - we've added a unit test for the specific problem we found on our branch.

pnorman added a commit to pnorman/osm2pgsql that referenced this issue Oct 25, 2014
Also increments the version to 0.87.0

Closes osm2pgsql-dev#187

Fixes osm2pgsql-dev#156
Fixes osm2pgsql-dev#186
Fixes osm2pgsql-dev#105
Fixes osm2pgsql-dev#111
@pnorman pnorman closed this as completed Oct 25, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants