)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"a14083792f8aa7a791987f8ffdb683eaf3ab9683","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"7243b137_61b66172","updated":"2024-02-23 12:42:48.000000000","message":"I know this has been hashed and rehashed elsewhere before, but I really think it\u0027s unlikely that one of the versions between the lowest supported version and the highest supported version would be broken without one of those goal posts also showing a problem. I would love to see some of those middle versions removed from at least some of the runs to reduce CI load. Like maybe for the initial submit run all tests, but for the merge only run the upper and lower versions, or vice versa.\n\nJust sharing my 2 cents.","commit_id":"2a29c10e6ab9ecac7eb264268154edf479289103"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"4e5e0b9ccfeba197c1adfd758f61a9214ba724f9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"586ff619_9a31e9bd","in_reply_to":"7243b137_61b66172","updated":"2024-02-23 19:03:21.000000000","message":"if we have versioned constraints this may happen. like if we have a new library that is only present for py \u003e\u003d 3.9, but later drops support for py3.9, it won\u0027t be noticed by only running 3.8 and 3.11 tests. having a delta between voting check and gate jobs has turned out to not be a good idea in multiple occasions, too.\n\nalso the uc checks are pretty fast compared to all the other tests that we have, so I don\u0027t think that cleaning them up should have high impact","commit_id":"2a29c10e6ab9ecac7eb264268154edf479289103"}]}
