[hint] [sru] autopkgtest regressed as an API key is now required

Bug #1831443 reported by Dimitri John Ledkov
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libgeo-coder-googlev3-perl (Ubuntu)
Fix Released
Undecided
Unassigned
Xenial
Invalid
Undecided
Unassigned
Bionic
Fix Released
Undecided
Unassigned

Bug Description

libgeo-coder-googlev3-perl uses a remote Google Maps service, which has started to require unique API keys.

As there is no API key for the autopkgtests, they have started to fail.

Autopkgtests for 0.16-1 will thus now always fail and should be hinted as expected failure.

In 0.17-1 networked tests have been disabled during autopkgtests, and I'm proposing to SRU such a fix to bionic too.

[Impact]

 * Unbreak autopkgtests by disabling networked tests due to remote service requiring authentication API tokens.

[Test Case]

 * autopkgtests should pass

[Regression Potential]

 * as networked tests are no longer performed, further regressions in utilising the remote service will not be caught.

[Hints]

 bionic: force-badtest libgeo-coder-googlev3-perl/0.16-1
 xenial: force-badtest libgeo-coder-googlev3-perl/0.14-1

Changed in libgeo-coder-googlev3-perl (Ubuntu):
status: New → Fix Released
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

At http://autopkgtest.ubuntu.com/packages/libgeo-coder-googlev3-perl/bionic/amd64

you can see a test triggered in -release/-updates pocket only, with a triggered by glibc, to show the regression in the release pocket alone.

Revision history for this message
Steve Langasek (vorlon) wrote :

Hint added for bionic.

No hint needed for xenial; per http://autopkgtest.ubuntu.com/packages/libg/libgeo-coder-googlev3-perl the xenial version of the package has no autopkgtest.

We should not do an SRU of this solely for the autopkgtest update.

Changed in libgeo-coder-googlev3-perl (Ubuntu Bionic):
status: New → Fix Released
Changed in libgeo-coder-googlev3-perl (Ubuntu Xenial):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.