It seems to rarely update and when it does, it incorrectly uses fully defined paths instead of relative ones.
First thing that looks quite wrong, it hits a 401 error on gerrit:
Traceback (most recent call last): File "/home/gilles/checkupdate.py", line 59, in <module> if check_if_existing_change(): File "/home/gilles/checkupdate.py", line 54, in check_if_existing_change results = gerrit_api.get('/changes/?q=topic:%s+is:open' % topic) File "/home/gilles/.local/lib/python2.7/site-packages/pygerrit2/rest/__init__.py", line 165, in get decoded_response = _decode_response(response) File "/home/gilles/.local/lib/python2.7/site-packages/pygerrit2/rest/__init__.py", line 60, in _decode_response response.raise_for_status() File "/home/gilles/.local/lib/python2.7/site-packages/requests/models.py", line 940, in raise_for_status raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 401 Client Error: Unauthorized for url: https://gerrit.wikimedia.org/r/a/changes/?q=topic:perfsite-autoupdate+is:open
Possibly due to the attack mitigations that have been put in place on our gerrit instance? Accessing that URL locally is fine, but fails with that 401 from the WMCS machine. Could be throttling of some kind.
Hmm yes, it appears that it's become impossible to use Basic auth with our gerrit instance: T218750: Re-enable use of Gerrit HTTP token to push patchsets I don't see the option for an HTTP password anymore. And interacting with gerrit has become an SSH-only affair as of late. This is unfortunate as I don't think the pygerrit2 library supports SSH auth.