We got an outage with our container provider. The machine was overloaded then the service crashed. The timeout result is because the Ansible play took far more time than expected. We've restarted the service and I believe that this is fixed. So I'll close the issue, please re-open if needed.

Actually, there is another instance of this issue:

https://src.fedoraproject.org/rpms/ruby/pull-request/179

Was it during the same window?

Right, I mixed with another deployment of Zuul with a similar container provider where we got an outage earlier today and for this one the service was still up and is still up and running but it seems there are some slowness. We need to investigate. Thanks for the report !

We could increase the timeout temporarily to get a result and check what is taking so long. It looks like this job has been flirting with the maximum run-time for a while already: https://fedora.softwarefactory-project.io/zuul/builds?job_name=rpm-rpminspect&project=rpms/ruby

Perhaps this is expected and we should raise the limit globally?

No worries.

BTW if there is similar issue as in #480, it would be no wonder rpminspect takes twice as long. I think that it could be easy to confirm my suspicion if the task displayed the name of inspected RPM.

Yes you are right that's a similar issue :/ and why the job took longer now

2024-07-10 10:15:39.552571 | LOOP [rpm-artifact-url : Get packages download urls]
2024-07-10 10:15:48.009726 | container | https://fedora.softwarefactory-project.io/logs/78/178/ca13a515893b6810288c9b589d6abb26438f757d/check/rpm-scratch-build/92208c7/repo/ruby-3.3.4-11.fc41.x86_64.rpm
2024-07-10 10:15:48.010461 | container | https://fedora.softwarefactory-project.io/logs/78/178/ca13a515893b6810288c9b589d6abb26438f757d/check/rpm-scratch-build/92208c7/repo/ruby-3.3.4-11.fc41.x86_64.rpm
2024-07-10 10:15:48.010650 | container | ok: Item: ruby-3.3.4-11.fc41 Runtime: 0:00:01.301704
2024-07-10 10:15:55.410359 | container | https://fedora.softwarefactory-project.io/logs/78/178/ca13a515893b6810288c9b589d6abb26438f757d/check/rpm-scratch-build/92208c7/repo/ruby-bundled-gems-3.3.4-11.fc41.x86_64.rpm
2024-07-10 10:15:55.414648 | container | https://fedora.softwarefactory-project.io/logs/78/178/ca13a515893b6810288c9b589d6abb26438f757d/check/rpm-scratch-build/92208c7/repo/ruby-bundled-gems-3.3.4-11.fc41.x86_64.rpm
2024-07-10 10:15:55.414765 | container | ok: Item: ruby-bundled-gems-3.3.4-11.fc41 Runtime: 0:00:01.153832

I'll land https://pagure.io/zuul-distro-jobs/pull-request/152 which is also a workaround change. I've tested with https://src.fedoraproject.org/rpms/python-gear/pull-request/66#comment-208854 and the rpms fact is no longer duplicated https://fedora.softwarefactory-project.io/zuul/build/2151103a6ae94df284920be47ade637c/console#1/0/6/container if we compare to the previous run (w/o the depends-on on the zuul-distro-jobs PR#152) https://fedora.softwarefactory-project.io/zuul/build/d010ceac1b5847b9a12a030104509f83/console#1/0/6/container

The change is merged. So I'll close this isssue. Please re-open if needed.