)]}'
{"zuul.d/layout.yaml":[{"author":{"_account_id":10969,"name":"Shnaidman Sagi (Sergey)","display_name":"Shnaidman Sagi","email":"sshnaidm@redhat.com","username":"sergsh"},"change_message_id":"5286b8d3ca07019bbe53fbd3364f5a30a56e300d","unresolved":true,"context_lines":[{"line_number":29,"context_line":"              - openstack-tox-py39"},{"line_number":30,"context_line":"        - tripleo-build-containers-ubi-8:"},{"line_number":31,"context_line":"            dependencies: *deps_unit_lint_cprovider"},{"line_number":32,"context_line":"        - tox-sanity-py36"},{"line_number":33,"context_line":"        - tox-sanity-py39"},{"line_number":34,"context_line":"    gate:"},{"line_number":35,"context_line":"      jobs:"},{"line_number":36,"context_line":"        - openstack-tox-pep8:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"cb53e51a_4df90cf0","line":33,"range":{"start_line":32,"start_character":8,"end_line":33,"end_character":25},"updated":"2021-08-19 09:46:49.000000000","message":"because ansible-test always changes and add another and another requirements for tests, I think it\u0027s worth to leave here a link to community issue where all these changes are published: https://github.com/ansible-collections/overview/issues/45\nActually it can be a significant burden of maintenance, not sure we should have it voting. Who will track this all the time?","commit_id":"14794dfe09450f198bcef3efda6ffde2b43a9f35"},{"author":{"_account_id":24162,"name":"Sorin Sbârnea","display_name":"zbr","email":"ssbarnea@redhat.com","username":"ssbarnea","status":"do not feed the troll 🥕"},"change_message_id":"d6ae545bf72427138997c016929737a90d18e01d","unresolved":true,"context_lines":[{"line_number":29,"context_line":"              - openstack-tox-py39"},{"line_number":30,"context_line":"        - tripleo-build-containers-ubi-8:"},{"line_number":31,"context_line":"            dependencies: *deps_unit_lint_cprovider"},{"line_number":32,"context_line":"        - tox-sanity-py36"},{"line_number":33,"context_line":"        - tox-sanity-py39"},{"line_number":34,"context_line":"    gate:"},{"line_number":35,"context_line":"      jobs:"},{"line_number":36,"context_line":"        - openstack-tox-pep8:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"7f96789b_0f1f4c18","line":33,"range":{"start_line":32,"start_character":8,"end_line":33,"end_character":25},"in_reply_to":"cb53e51a_4df90cf0","updated":"2021-09-01 11:00:06.000000000","message":"Let me rephrase it: soon you will not be able to publish new collections unless sanity check is passing, so any collection author MUST run sanity check, unless he wants to be unable to publish them.\n\nThe link you mentioned is irrelevant. There is no inherent problem with testing, newer versions become better at finding problems and CI jobs will break. The breakage is desired when happens for genuine reasons. Otherwise you can just remove all CI jobs and \"claim\" that everything is fine.","commit_id":"14794dfe09450f198bcef3efda6ffde2b43a9f35"}]}