After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 766714 - fails to run _xep, _search_lat_long in test_gcglib
fails to run _xep, _search_lat_long in test_gcglib
Status: RESOLVED DUPLICATE of bug 756311
Product: geocode-glib
Classification: Other
Component: general
Other Mac OS
: Normal normal
: ---
Assigned To: geocode-glib maintainer(s)
geocode-glib maintainer(s)
Depends on:
Reported: 2016-05-20 13:08 UTC by Justin Kim
Modified: 2016-10-13 17:18 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Justin Kim 2016-05-20 13:08:47 UTC
This would be a kind of question, rather than a bug report. (but, it could be)

When I run 'test-gcglib', it fails in two test functions which are modified by a commit, 'a90ea49 test-gcglib: Conform to reality', but I can't guess what is wrong in my side. In my local environment, the test is passed only if I revert the commit.

What should I check to get right test result?
Comment 1 Justin Kim 2016-05-20 13:12:01 UTC
Here are the results.

/geocode/xep-0080: **
ERROR:test-gcglib.c:207:test_xep: assertion failed (geocode_location_get_latitude (loc) == 51.2371416): (51.2371333 == 51.2371416)

/geocode/search_lat_long: **
ERROR:test-gcglib.c:341:test_search_lat_long: assertion failed (geocode_place_get_name (place) == "Santa Maria Del Rio, Santa Mar\303\255a del Rio"): ("Santa Maria Del Rio, Santa Mar\303\255a del R\303\255o" == "Santa Maria Del Rio, Santa Mar\303\255a del Rio")
Comment 2 Philip Withnall 2016-10-13 17:18:02 UTC
The failure is because the tests run queries against the online Nominatim instance, whose database is regularly updated, which can sometimes change the test results. When that happens, the tests need to be updated.

This is fixed by the patches in bug #756311, which allow the tests to be run offline against saved results.

*** This bug has been marked as a duplicate of bug 756311 ***