https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-rawhide-pr-pipeline/detail/fedora-rawhide-pr-pipeline/1908/pipeline/ was triggered by https://src.fedoraproject.org/rpms/python27/pull-request/1 but the PR only shows simple-koji-ci.
Is something broken?
https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-rawhide-pr-pipeline/detail/fedora-rawhide-pr-pipeline/1909/pipeline/ https://src.fedoraproject.org/rpms/python-virtualenv/pull-request/12
https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-rawhide-pr-pipeline/detail/fedora-rawhide-pr-pipeline/1906/pipeline/ https://src.fedoraproject.org/rpms/python34/pull-request/39
https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-rawhide-pr-pipeline/detail/fedora-rawhide-pr-pipeline/1910/pipeline https://src.fedoraproject.org/rpms/python-setuptools/pull-request/25#
This seems like a consistent breakage.
https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-rawhide-pr-pipeline/detail/fedora-rawhide-pr https://src.fedoraproject.org/rpms/python3/pull-request/132
This also happens with f31, f30 and f29. Not just rawhide.
This must be a loopabull issue (the thing which updates the PR flags based on the fedmsg messages), because I see correctly dist-git-pr.test.complete messages here:
https://apps.fedoraproject.org/datagrepper/raw?topic=org.centos.prod.ci.dist-git-pr.test.complete&delta=127800
https://pagure.io/fedora-infrastructure/issue/8160
thanks, this works now
Metadata Update from @churchyard: - Issue status updated to: Closed (was: Open)
Metadata Update from @churchyard: - Issue status updated to: Open (was: Closed)
and apparently, broken again
it is, see https://pagure.io/fedora-infrastructure/issue/8160 :(
Yes, i'm watching that and I've closed this ticket when @kevin fixed it, but later reopened when it got broken again. I will now keep this ticket open until that one is closed to avoid further spam.
@churchyard I think we fixed this now, could you try again? :)
Metadata Update from @bookwar: - Issue tagged with: bug