)]}'
{".zuul.yaml":[{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"44c6e6787cc6de03baf83e8ea30371c1030026d4","unresolved":true,"context_lines":[{"line_number":960,"context_line":"        - nova-tox-py313-threading"},{"line_number":961,"context_line":"        - openstack-tox-cover:"},{"line_number":962,"context_line":"            # Allow more time for unit and functional tests to run."},{"line_number":963,"context_line":"            timeout: 6000"},{"line_number":964,"context_line":"    gate:"},{"line_number":965,"context_line":"      jobs:"},{"line_number":966,"context_line":"        - nova-live-migration"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"85ef3535_bddf25bc","line":963,"updated":"2026-04-13 16:34:06.000000000","message":"we seem to be right on the boarder between slow host passing and failing \nfaster provider noes are finish 30mins ahead fo the slower ones.\nso if this still is a problem after this bump we can consider have separate coverage jobs for unit vs funcitonl or explore the althernitive coverage backends\nthat stephen mentioned.\n\nits been a while since i looked but i belvie the tradefoff withthe fast backend is we loose branch tacking unless we either disabel evently or run it under py3.14 or somethign like that.\n\ni.e. the alternive need more review bcasue it woudl not be one for one partiy with the existing execution model.","commit_id":"c380986e75c3d8f72a83e1bf7a7b15b30a8c58f7"}]}