)]}'
{"playbooks/horizon-devstack-integration/run.yaml":[{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"a3ce6153a7c7e990b91ed9c898ee008042d11a6f","unresolved":false,"context_lines":[{"line_number":6,"context_line":"  roles:"},{"line_number":7,"context_line":"    - tox"},{"line_number":8,"context_line":"      vars:"},{"line_number":9,"context_line":"        tox_envlist: venv"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"ff570b3c_3a02d60a","line":9,"updated":"2020-05-22 11:53:47.000000000","message":"I am really confused with this change. We need to run \"tox -e integration\" to run the integration tests properly. What does this change mean?\n\nwe specifies \"tox_envlist: integration\" in .zuul.yaml [1] and \"integration\" test env specifies \"envdir \u003d {toxdir}/venv\".\nIIRC the current \"tox\" role does not support \"envdir\" in tox.ini, but I am not sure it is related to this commi.\n\nAnyway, while I read the commit message, I haven\u0027t understood what behavior would be discouraged. Could you clarify it?\n\n[1] https://opendev.org/openstack/horizon/src/branch/master/.zuul.yaml#L74","commit_id":"945600394adf5330ca65ca0ad9ebeb82a4ca81ef"},{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"8976b2e0c4c87c1be126532e8177109554de8d43","unresolved":false,"context_lines":[{"line_number":6,"context_line":"  roles:"},{"line_number":7,"context_line":"    - tox"},{"line_number":8,"context_line":"      vars:"},{"line_number":9,"context_line":"        tox_envlist: venv"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"ff570b3c_fa45fe44","line":9,"in_reply_to":"ff570b3c_3a02d60a","updated":"2020-05-22 12:00:13.000000000","message":"tox now supports envdir for sibling installation (since earlier this week).\n\nThat envdir might have confused me...","commit_id":"945600394adf5330ca65ca0ad9ebeb82a4ca81ef"}]}