I thought this wasn't possible as I didn't think the Koji client library was thread-safe, but it seems like it actually is, as it uses requests. I tested this out locally and it looks like it's OK. We noticed this "check whether this build actually ran for our arch" code generated a lot of load on Koji when a 400+ package qt6 update hit testing and both openQA instances span up a bunch of jobs, many of which hit setup_repos simultaneously. I hope this will mitigate it a bit in future. Signed-off-by: Adam Williamson <awilliam@redhat.com> |
||
|---|---|---|
| .. | ||
| check-release.py | ||
| ostree-parse-pungi-ib.py | ||
| ostree-parse-pungi.py | ||
| setup_repos.py | ||
| testdata.tar.gz | ||
| updvercheck.py | ||
| video.ogv | ||