-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
.ebg file empty and no error #1905
Comments
Yes you are correct. Already tracked in #1682. Closing as duplicate. We're in the progress of cleaning up these little annoyances in Thanks for reporting! |
Ok, I didn't find any related bugs, thanks for the reference. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am following the issue #1846. I had the same error while running osrm-prepare (), and watching the disc usage graph, I saw the free space eaten, but osrm-extract exited with code 0, resulting in osrm-prepare to be executed but with an empty .ebg file.
I think osrm-extract can detect if it can't write in this file and exit with a non-zero code.
The text was updated successfully, but these errors were encountered: