)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"32d78c29605cfe01371531e56713dcda6889dc3d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"c3450cd6_62c39572","updated":"2024-01-18 23:46:38.000000000","message":"Curious failures -- for py38:\n```\n  installing to build/bdist.linux-x86_64/wheel\n  running install\n  [pbr] Writing ChangeLog\n  [pbr] Generating ChangeLog\n  [pbr] ChangeLog complete (0.0s)\n  [pbr] Generating AUTHORS\n  [pbr] AUTHORS complete (0.1s)\n  running install_lib\n  running install_egg_info\n  Copying pbr.egg-info to build/bdist.linux-x86_64/wheel/pbr-0.0-py3.8.egg-info\n  running install_scripts\n  creating build/bdist.linux-x86_64/wheel/pbr-0.0.dist-info/WHEEL\n  creating \u0027/tmp/pip-wheel-i4wvg4rv/pbr-0.0-py2.py3-none-any.whl\u0027 and adding \u0027build/bdist.linux-x86_64/wheel\u0027 to it\n  adding \u0027pbr/__init__.py\u0027\n  ...\n  adding \u0027pbr/tests/base.py\u0027\n  adding \u0027pbr-0.0.dist-info/RECORD\u0027\n  removing build/bdist.linux-x86_64/wheel\n  error: [Errno 2] No such file or directory: \u0027build/bdist.linux-x86_64/wheel\u0027\n  error: subprocess-exited-with-error\n  \n  × python setup.py bdist_wheel did not run successfully.\n  │ exit code: 1\n  ╰─\u003e See above for output.\n  \n  note: This error originates from a subprocess, and is likely not a problem with pip.\n```\npy310:\n```\n  installing to build/bdist.linux-x86_64/wheel\n  running install\n  [pbr] Writing ChangeLog\n  [pbr] Generating ChangeLog\n  [pbr] ChangeLog complete (0.0s)\n  [pbr] Generating AUTHORS\n  [pbr] AUTHORS complete (0.1s)\n  running install_lib\n  running install_egg_info\n  Copying pbr.egg-info to build/bdist.linux-x86_64/wheel/pbr-0.0-py3.10.egg-info\n  running install_scripts\n  creating build/bdist.linux-x86_64/wheel/pbr-0.0.dist-info/WHEEL\n  creating \u0027/tmp/pip-wheel-4w0n2hc1/pbr-0.0-py2.py3-none-any.whl\u0027 and adding \u0027build/bdist.linux-x86_64/wheel\u0027 to it\n  adding \u0027pbr/__init__.py\u0027\n  ...\n  adding \u0027pbr/tests/test_version.py\u0027\n  adding \u0027pbr-0.0.dist-info/RECORD\u0027\n  error: [Errno 2] No such file or directory: \u0027build/bdist.linux-x86_64/wheel/pbr/tests/testpackage/CHANGES.txt\u0027\n  error: subprocess-exited-with-error\n  \n  × python setup.py bdist_wheel did not run successfully.\n  │ exit code: 1\n  ╰─\u003e See above for output.\n  \n  note: This error originates from a subprocess, and is likely not a problem with pip.\n```\ntempest-full:\n```\n2024-01-18 22:54:03.766769 | controller | + inc/python:pip_install:283               :   sudo -H http_proxy\u003d https_proxy\u003d no_proxy\u003d PIP_FIND_LINKS\u003d SETUPTOOLS_SYS_PATH_TECHNIQUE\u003drewrite /usr/local/bin/pip2.7 install -c /opt/stack/requirements/upper-constraints.txt -e /opt/stack/glance\n...\n2024-01-18 22:54:06.056320 | controller | glance requires Python \u0027\u003e\u003d3.8\u0027 but the running Python is 2.7.17\n```\nThat last one cracks me up...\n\nFWIW, running `tox -e py310,py311` locally results in 20+ failures for each interpreter unless I add `--serial` to the stestr command. Maybe I should propose that as a separate change -- but the same tempest-full failure on https://review.opendev.org/c/openstack/pbr/+/906069 makes me think any new patch is unlikely to pass tests until that\u0027s resolved.","commit_id":"049282adbbd702ae436e6473be9a94e639a63c0e"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"c65353825886e28808f6ebe779edb4ca458f93cc","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"5dc31054_57aca6f0","updated":"2024-01-24 03:24:59.000000000","message":"LGTM. Thanks !","commit_id":"049282adbbd702ae436e6473be9a94e639a63c0e"},{"author":{"_account_id":31245,"name":"Daniel Bengtsson","email":"dbengt@redhat.com","username":"damani42"},"change_message_id":"c1122b0aa4acbca1e290771c9110c6c4532d1142","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"11ee3f38_0a64a207","updated":"2024-01-23 11:56:56.000000000","message":"recheck","commit_id":"049282adbbd702ae436e6473be9a94e639a63c0e"},{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"9cf9b303c8dff244702cbb89cae618c185988166","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"dd5a887c_18d0b7b2","updated":"2024-01-19 21:46:25.000000000","message":"recheck\n\nThe tempest-full job should be fixed now; we\u0027ll see if we can have better luck with the others this time","commit_id":"049282adbbd702ae436e6473be9a94e639a63c0e"}]}