pkg-perl-maintainers team mailing list archive

[Skia <2025645@xxxxxxxxxxxxxxxxxx>]

Well, indeed that seems kind of infra related, but not as in "specific to the infra".
The good thing is that is reproduces locally quite easily (from the libwww-mechanize-perl sources):

autopkgtest . --env=http_proxy='http://squid.internal:3128' -- qemu
autopkgtest-oracular-amd64.img

For that to "work" and reproduce the issue, you need to have the
Canonical VPN set up, so that `squid.internal` works correctly. You'll
see that setting `http_proxy` to a non-working proxy doesn't work,
because `apt` can't install anything and the testbed cannot be
initialized. I guess setting up a local proxy with proper configuration
could also do the trick.

The interesting part, is that it reproduces with a local build of the
package, like above, but not when the package comes from the archive
itself. This passes successfully without trouble:

autopkgtest libwww-mechanize-perl
--env=http_proxy='http://squid.internal:3128' -- qemu autopkgtest-
oracular-amd64.img

This makes me think that the issue actually lies within autopkgtest
itself. I've reproduced the issue on both the plucky version of
autopkgtest (5.38ubuntu1) and on master (very close to 5.42).

I'll set this bug as also affecting autopkgtest so that we have it on
our radar too.

** Also affects: autopkgtest (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: autopkgtest (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Debian
Perl Group, which is subscribed to libwww-mechanize-perl in Ubuntu.
https://bugs.launchpad.net/bugs/2025645

Title:
  t/local/referer.t blocking forever during autopkgtests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2025645/+subscriptions