)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"f05f1600615dda3a3e14157e6e9f21cc1fe61a53","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"f1ebe18d_b9dea0de","updated":"2025-02-10 19:12:16.000000000","message":"This change is failing in pre-run on its devstack jobs due to devstack expecting etc/tacker/rootwrap.d/ to exist but it was removed by this change:\n\n`install: cannot stat \u0027/opt/stack/tacker/etc/tacker/rootwrap.d/*\u0027: No such file or directory`\n\nThis is problematic because failures in pre-run are retried up to three times. Since this error is deterministic we retry all three times. Additionally tacker runs 33 such jobs on this change. Each of these jobs appears to use 4 nodes each. If we do some math that means this single change required 7 (non devstack job nodes) + 33 * 4 * 3 \u003d 403 nodes. That is roughly half of our total theoretical capacity.\n\nIt would be appreciated if tacker could look at refactoring its CI jobs to avoid consuming such a large quantity of resources from a single change. Options include merging jobs together. I noticed there appear to be similar jobs that simply run different test cases against the same devstack setup for example. We could trade an hour of setup time doubled for the runtime of those test cases. Another option would be to stop running devstack in pre-run. It seems like changes to tacker do affect devstack directly and having devstack retry over and over is probably not appropriate in those cases. There are probably more ideas that can be come up with too but these are the things I noticed upfront.","commit_id":"ca7faad1236d7181a1f91f8cfef031d190265de5"},{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"fc597c60be4b47635ee639503d7d029ecc708e97","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"eeb7445f_b484ebc2","in_reply_to":"f1ebe18d_b9dea0de","updated":"2025-02-10 19:15:02.000000000","message":"Note the math above is `7 + 33 * 4 * 3 \u003d 403`. The `*\u0027s` got consumed by the gerrit comment formatting.","commit_id":"ca7faad1236d7181a1f91f8cfef031d190265de5"},{"author":{"_account_id":25701,"name":"Yasufumi Ogawa","email":"yasufum.o@gmail.com","username":"yasufum"},"change_message_id":"9ec3439511797e145aea430699d35e59fe666f29","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"ca472c6a_624f94c7","updated":"2025-02-25 08:29:53.000000000","message":"Thank you for the update. Privsep for tacker was under discussion for using it later, but disappeared. We don\u0027t have any plan so that and the change is acceptable for now.","commit_id":"d83ba23b22126754e048c77ea8c44b73e6373950"}]}