Skip Menu |

This queue is for tickets about the Geo-Coder-Googlev3 CPAN distribution.

Report information
The Basics
Id: 122485
Status: resolved
Priority: 0/
Queue: Geo-Coder-Googlev3

People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 0.15
Fixed in: 0.16



Subject: bounds test started to fail
Sample fail report: http://www.cpantesters.org/cpan/report/7168cde4-6863-11e7-b6db-bcdb857a4f17 Test log output: # Failed test at t/geocode.t line 181. # '34.2048586' # >= # '42.108083' # Failed test at t/geocode.t line 183. # '-118.5739621' # >= # '-87.7359' # Looks like you failed 2 tests of 67. t/geocode.t .. The failing test is actually using the same parameters as in Google's documentation (without an api key): https://developers.google.com/maps/documentation/geocoding/intro#Viewports A first analysis shows that the results of these URLs are different depending on the user agent: I get a "correct" result using Firefox, but a "wrong" one using Chromium, Safari, lwp-request, or curl.
On 2017-07-14 15:20:44, SREZIC wrote: Show quoted text
> Sample fail report: http://www.cpantesters.org/cpan/report/7168cde4- > 6863-11e7-b6db-bcdb857a4f17 > > Test log output: > > # Failed test at t/geocode.t line 181. > # '34.2048586' > # >= > # '42.108083' > > # Failed test at t/geocode.t line 183. > # '-118.5739621' > # >= > # '-87.7359' > # Looks like you failed 2 tests of 67. > t/geocode.t .. > > The failing test is actually using the same parameters as in Google's > documentation (without an api key): > https://developers.google.com/maps/documentation/geocoding/intro#Viewports > A first analysis shows that the results of these URLs are different > depending on the user agent: I get a "correct" result using Firefox, > but a "wrong" one using Chromium, Safari, lwp-request, or curl.
The failing test was made a TODO test in 0.16. Currently the test again works, so the $TODO was removed for the next release.