but https://src.fedoraproject.org/rpms/python2/pull-request/54 has started.

There are some presumably random starts but not all of them. The machinery seem either flaky or extremely slow. For example I don't know if this has been missed or is still waiting after several hours:

https://src.fedoraproject.org/tests/python/pull-request/21#comment-42061

@jimbair I couldn't find the message from the comment above on https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/job/fedora-pr-comment-trigger/

Do you think this could be related FedoraMessaging as since yesterday we started to trigger on it instead of FedMSg?

Meanwhile I've opened an infra issue to track this: https://pagure.io/fedora-infrastructure/issue/8846

Meanwhile, would you be able to manually strat https://src.fedoraproject.org/tests/python/pull-request/21 please?

Meanwhile, would you be able to manually strat https://src.fedoraproject.org/tests/python/pull-request/21 please?

I see it is running: https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-rawhide-pr-pipeline/detail/fedora-rawhide-pr-pipeline/3225/pipeline/

Indeed. Thanks!

@churchyard we reverted the triggers to use FedMSg, the jobs should be starting correctly now...

Thanks. Keeping open (as I understand this is not the proper solution), but feel free to close if you are OK tracking it in the infra ticket.

I''ll close this issue and we continue to track the FedoraMessaging issue on infra ticket.