Autopkgtest failure with https_proxy or http_proxy set
Bug #1972888 reported by
Olivier Gayot
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libcloud (Debian) |
Fix Released
|
Unknown
|
|||
libcloud (Ubuntu) |
Fix Released
|
Undecided
|
Olivier Gayot |
Bug Description
Autpkgtest is failing for libcloud when either http_proxy or https_proxy is set since the move to upstream version 3.4.1.
In the previous version (3.2.0-2), Debian applied a patch to disable some of the tests that are failing now.
test/test_
test/test_http.py includes new tests which execute HTTP queries to the loopback interface. This can't work with proxies (unless the proxy is on the loopback interface).
test/compute/
Changed in libcloud (Ubuntu): | |
assignee: | nobody → Olivier Gayot (ogayot) |
description: | updated |
description: | updated |
Changed in libcloud (Debian): | |
status: | Unknown → New |
Changed in libcloud (Debian): | |
status: | New → Fix Released |
To post a comment you must log in.
Added debdiff that applies multiple patches to:
1. fix closing sequence of the HTTP server in tests. This is not strictly necessary to fix the autopkgtest failures but other patches (i.e., see 2.) rely on the name of the function tearDownClass to be fixed (it used to be misspelled tearDownCls and code in there would be unreachable). Forwarded upstream and was merged yesterday.
2. handle http_proxy and https_proxy variables in various tests. Patches forwarded upstream (not merged currently)
3. disable the test that requires to be online (no need to uptream this one)
I will forward these patches to Debian (and update the dep3 headers accordingly) once I'm sure all autopkgtest failures are fixed.