)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":5689,"name":"Masayuki Igawa","email":"masayuki@igawa.io","username":"igawa"},"change_message_id":"f9445f45ab0cc2507b5d882a19ff75d9a6fb918b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"f3729124_125bea63","updated":"2023-03-01 08:28:02.000000000","message":"I\u0027m a bit confused. And, I\u0027m not sure why the CI passed in https://review.opendev.org/c/openstack/tempest/+/875264 without this patch, actually..\n\nupper-constraints.txt doesn\u0027t affect for tempest..? ","commit_id":"e2315c1cf55b8eb7996c61bed85313d5ff90d07f"},{"author":{"_account_id":16312,"name":"Alfredo Moralejo","email":"amoralej@redhat.com","username":"amoralej"},"change_message_id":"64b19142d786d678a4bc34cdcbe93ee8514e4e2a","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"5f0de32b_f5d13f48","updated":"2023-03-02 18:06:28.000000000","message":"This change makes tempest compatible only with antelope release as the u-c for zed is 4.14.0 and wallaby, i.e. is 3.2.0. Is that expected?. I\u0027m not sure what\u0027s the backwards compatibility policy for tempest.","commit_id":"e2315c1cf55b8eb7996c61bed85313d5ff90d07f"},{"author":{"_account_id":22873,"name":"Martin Kopec","email":"mkopec@redhat.com","username":"mkopec"},"change_message_id":"114a623259def19e69e3b943e8e36759cb87a172","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"d213d5de_df178bd6","updated":"2023-03-01 09:50:58.000000000","message":"good catch, thanks","commit_id":"e2315c1cf55b8eb7996c61bed85313d5ff90d07f"},{"author":{"_account_id":22873,"name":"Martin Kopec","email":"mkopec@redhat.com","username":"mkopec"},"change_message_id":"dd12a26313ee0918ceccbc14c20e0f3ebfff24ef","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"4c185d1c_5c9d12f4","updated":"2023-03-01 13:58:06.000000000","message":"recheck not related issue plus a timeout ","commit_id":"e2315c1cf55b8eb7996c61bed85313d5ff90d07f"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"042ab5c0a2075536c3b2bbae8000af090f978c62","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"1a4a9996_89706119","in_reply_to":"5f0de32b_f5d13f48","updated":"2023-03-02 22:43:53.000000000","message":"we need to support till xena as Tempest master do support stable/xena onwards branches. stable/xena has jsonschema 3.2.0 only https://github.com/openstack/requirements/blob/stable/xena/upper-constraints.txt#L548\n\nWe need to avoid such bumping unless something is failing.","commit_id":"e2315c1cf55b8eb7996c61bed85313d5ff90d07f"},{"author":{"_account_id":22873,"name":"Martin Kopec","email":"mkopec@redhat.com","username":"mkopec"},"change_message_id":"114a623259def19e69e3b943e8e36759cb87a172","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"68703e47_051cc574","in_reply_to":"f3729124_125bea63","updated":"2023-03-01 09:50:58.000000000","message":"it worked because the new (as the previous requirements allowed that) - 4.16.0 - version was installed - that\u0027s a version which is \u0027recommended\u0027 for master by the upper constraints - https://opendev.org/openstack/requirements/raw/branch/master/upper-constraints.txt\n\nThis patch simply bumps the minimum version so that a user is not able to install older jsonschema version than 4.16.0 by any chance (if upper constraints are not used or the user wants to override it) because things will fail as tempest would attempt to use a functionality from jsonschema which isn\u0027t available in \u003c 4.16.0.","commit_id":"e2315c1cf55b8eb7996c61bed85313d5ff90d07f"}]}