[Bug 1892832] Re: dnspython 2.0.0-1 fails IPv6 autopkgtests

[Lukas Märdian]

Apparently it is not enough to disable the IPv6/UDP tests, as the
failures were not resolved by disabling those tests in -1ubuntu1.

I was not able reproduce the exact same failures locally, but I was able
to produce some more other failures, related to DoH/DNS-over-HTTPS and
unrelated to IPv6/UDP when using squid.proxy for HTTP/HTTPS connections.

As there are quite a few problems with this test suite on Ubuntu's
autopkgtest infra, I suggest to disable all online testing for dnspython
(the test suite is prep'ed for that) and use only the self-contained
tests. This will skip 92 out of 861 tests (~11%).

See attached -1ubuntu2 debdiff.

** Patch added: "dnspython_2.0.0-1ubuntu2.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/dnspython/+bug/1892832/+attachment/5408362/+files/dnspython_2.0.0-1ubuntu2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dnspython in Ubuntu.
https://bugs.launchpad.net/bugs/1892832

Title:
  dnspython 2.0.0-1 fails IPv6 autopkgtests

Status in dnspython package in Ubuntu:
  New

Bug description:
  Currently dnspython 2.0.0-1 is stuck in groovy-proposed due to its own
  autopkgtests failing. After investigating a bit further, it can be
  seen that the failing (and hanging) tests are ones related to UDP DNS
  queries using IPv6, which were not tested in the previous dnspython
  versions. This particularly means the testQueryUDP* tests from
  tests_query and tests_async (but there's more). The testing suite
  tries to be as smart as possible and checks for IPv6 connectivity
  before trying to validate IPv6, but on our infrastructure those checks
  pass but the UDP tests do not.

  This rises the question if the autopkgtest infrastructure (with the
  network proxy) simply intervenes in the testing, causing those tests
  to fail, or is this feature broken in Ubuntu. It's worth noting that
  these autopkgtests are passing fine on Debian.

  I have tried preparing an IPv6 setup to check which one is it, but sadly I was unable to get one configured properly - no IPv6 support from my ISP, nor was I able to get IPv6 working via a VPN.
  We need someone to check that the failing bits work on a regular setup or not - if yes, we can then simply disable the IPv6 checks in the package and let it migrate.

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