)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"599c5b5ad6ab75b43cdcc07e65907dba12052b0c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"cc950095_768a4796","updated":"2026-07-16 22:56:30.000000000","message":"lgtm, test passing fine https://zuul.opendev.org/t/openstack/build/a523cfbd59324849b377bcaba734f09e/log/job-output.txt#35290","commit_id":"406633de5471ef4834c65d2ec5a682d3251251a7"},{"author":{"_account_id":10459,"name":"Luigi Toscano","email":"ltoscano@redhat.com","username":"ltoscano"},"change_message_id":"dca7de2b6eeec68139cbec0333a9e8a75dce526a","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"7ff9c002_8c4b1d5f","updated":"2026-07-16 09:02:09.000000000","message":"recheck\n\nanother unrelated tempest failure in tempest-full-preprov-creds, setUpClass (tempest.api.compute.servers.test_server_actions.ServerActionsV293TestJSON). The tests changed by this patch are not executed by that job at all.","commit_id":"406633de5471ef4834c65d2ec5a682d3251251a7"},{"author":{"_account_id":10459,"name":"Luigi Toscano","email":"ltoscano@redhat.com","username":"ltoscano"},"change_message_id":"d5130519ef172ee1b8ebb00e6c9f8a461f0ff4f9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"b4919902_2eabe381","updated":"2026-07-16 06:35:10.000000000","message":"recheck\n\nunrelated failure in tempest-slow-py3, namely tempest.scenario.test_instances_with_cinder_volumes.TestInstancesWithCinderVolumes.test_instances_with_cinder_volumes_on_all_compute_nodes.  Maybe a concurrency issue? Isn\u0027t 4 a bit high for these slow tests? But anyway, the 2 tests affected by this change passed.","commit_id":"406633de5471ef4834c65d2ec5a682d3251251a7"}]}