On 3/23/22 11:30, Andreas Beckmann wrote:
Source: nova
Version: 2:25.0.0~rc1-1
Severity: important
Hi,
nova/experimental started to FTBFS in my build environment with
FAIL:
nova.tests.unit.api.openstack.test_requestlog.TestRequestLogMiddleware.test_logs_mv
nova.tests.unit.api.openstack.test_requestlog.TestRequestLogMiddleware.test_logs_mv
----------------------------------------------------------------------
testtools.testresult.real._StringException: pythonlogging:'': {{{2022-03-22 14:22:40,758
INFO [nova.service] Updating service version for <MagicMock
name='get_by_host_and_binary().binary' id='139820781372032'> on <MagicMock
name='get_by_host_and_binary().host' id='139820781363664'> from 1 to 61}}}
[...]
File "/usr/lib/python3/dist-packages/wsgi_intercept/_urllib3.py", line 36,
in install
raise RuntimeError(
RuntimeError: http_proxy or https_proxy set in environment, please unset
debian/rules should probably clean the environment before runnign the tests
if that is needed.
External network access will probably be no longer available, though.
Hi,
As you can see, the fail is in wsgi_intercept, which is a library to
intercept WSGI calls, in order to mock the reply from a web server.
Everything is normal here, and working as expected.
I don't see why I should act on this. There is no requirements in Debian
that a package should be buildable with "http_proxy or https_proxy set
in environment".
Could you explain?
Cheers,
Thomas Goirand (zigo)
