-
-
Notifications
You must be signed in to change notification settings - Fork 226
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
FATAL ERROR: 138 regression(s) detected. #304
Comments
I encountered something similar on a planet build. Here is an example regression:
When I compare my local output to the public and dev APIs they seem to have the same "regressions" https://pelias.github.io/compare/#/v1/search?sources=wof&text=Citt%C3%A0+del+Vaticano%2C+Vatican |
Sorry for the possible double post... GH UI is giving me grief. These are integration tests testing the entire stack with real input data. Since the input data can change (planet-latest.osm.pbf, latest WOF, etc.), it follows that the expected output will change. I just ran the tests against north-america and get a handful of failures:
Most of them seem like the kind of thing I'd expect from changing input data. e.g.:
There's an argument to be made for pinning the tests to known input data, and then updating the inputs & tests in lockstep, but that might be more work for the maintainers. full output of north-america tests
|
Hi there,
I installed Pelias Planet build on my server with prepare extracts from Geoearth rather than preparing myself but i got some errors when i ran test script. What can be wrong in my configuration?
Describe the bug
Results are under the bellow:
Pass: 503
Improvements: 14
Expected Failures: 101
Placeholders: 0
Regressions: 138
Total tests: 756
Took 19113ms
Test success rate 81.75%
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: