)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":9708,"name":"Balazs Gibizer","display_name":"gibi","email":"gibizer@gmail.com","username":"gibi"},"change_message_id":"dca3c82276971a58257c050facca3fb52d72b40e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"8bd3cc2b_9fe1f1ef","updated":"2025-12-18 14:51:53.000000000","message":"Meh the issue is partly due to the test case itself. It mocks threading.Event.wait() which means all the threading.Event objects created in the testcase start behaving incorrectly and returning early. This causes that the looping call implementation also starts behaving incorrectly and even though the test supposed to wait for the looping call to finish the waiting does not happen causing the leaked call.\n\nhttps://github.com/openstack/nova/blob/3e5a2dbad73ff61d27db8750480e2c0b52133676/nova/tests/unit/virt/test_virt_drivers.py#L461\n\nThis only hits the threading backend as the eventlet loopingcall backend does not use threading.Event but eventlet.Event.","commit_id":"881b1251521e6e0586a5605e7f9fcd1da9c755af"}]}