)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"d6f93dbb437a01e7f7d1dca5b783bbcb88ab897a","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"d6aa325f_5b10d9e4","updated":"2025-06-04 09:12:54.000000000","message":"as long as we have constraints for py39 in u-c, we also need to keep verifying them, see https://review.opendev.org/c/openstack/requirements/+/948876 for context","commit_id":"9cd346026acc8179bebc2b40e2b060c10db33c37"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"c0663324eb0a9d3923b0d29c4b65a6b594798e30","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"56f9e5ea_5295fb39","updated":"2025-06-04 08:55:39.000000000","message":"could have been added the reason of this patch in the commit message o:) otherwise LGTM.\n\n(the reason is: py39 is not supported starting from 2025.2 Flamingo [1] hence projects dropping py39 version support from their setup.py, which makes this job fail.\n\n[1] https://governance.openstack.org/tc/reference/runtimes/2025.2.html )","commit_id":"9cd346026acc8179bebc2b40e2b060c10db33c37"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"5eb0502f92e2d6ebcadfd118e2dfb7f90e0e96a9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"9656a86b_8d3d22ef","in_reply_to":"61b6ff3c_9184df7d","updated":"2025-06-04 10:09:33.000000000","message":"Okay, I see now your comment Jens on the patch on top of this [1]. Thanks.\n\n[1] https://review.opendev.org/c/openstack/requirements/+/951657/2#message-a2b9e2366ce2ceb06e8a35b1e3b95ba55a9150d2","commit_id":"9cd346026acc8179bebc2b40e2b060c10db33c37"},{"author":{"_account_id":8313,"name":"Lajos Katona","display_name":"lajoskatona","email":"katonalala@gmail.com","username":"elajkat","status":"Ericsson Software Technology"},"change_message_id":"6fc9296c0abcc3f0e2b474112109452fc1a882c1","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"01d8c46f_6610dae8","in_reply_to":"9656a86b_8d3d22ef","updated":"2025-06-04 10:11:36.000000000","message":"thanks, I check it","commit_id":"9cd346026acc8179bebc2b40e2b060c10db33c37"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"1fd71fd628e1d4e4c651a6afaf96024822b06514","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"61b6ff3c_9184df7d","in_reply_to":"d6aa325f_5b10d9e4","updated":"2025-06-04 09:57:29.000000000","message":"does that mean that projects that dropped py39 support needs a revert for their patches? (e.g. openstacksdk requires python \u003e 3.9 already, so requirements-tox-py39-check-uc job fails when bumping upper constraints - see the patch on top of this) or should the requirements-tox-py39-check-uc job be set as non-voting?","commit_id":"9cd346026acc8179bebc2b40e2b060c10db33c37"}]}