a PR: https://src.fedoraproject.org/rpms/python3/pull-request/81
Tests results: https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-f29-pr-pipeline/detail/fedora-f29-pr-pipeline/19/pipeline https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-f29-pr-pipeline/detail/fedora-f29-pr-pipeline/18/pipeline
But those are not linked from Pagure.
Seems messages where not caught by the machinery that updates the flags. The complete messages were sent correctly as pipeline would not end successfully otherwise.
@churchyard does this happen a lot?
Metadata Update from @mvadkert: - Issue assigned to mvadkert
This happen always since I've reported this. Both Fedora Ci and Simple Koji CI as reported in https://pagure.io/fedora-ci/simple-koji-ci/issue/25
Seems loop-a-bull issue as a guess. I kindly asked @pingou to take a look, he will do that but he is travelling currenlty
Closing in favor of #23. The same thing. Fedmsg prod issue
Metadata Update from @mvadkert: - Issue status updated to: Closed (was: Open)
Metadata Update from @mvadkert: - Issue marked as depending on: #23
This is different. The CI job started, but there was no link.
Metadata Update from @churchyard: - Issue status updated to: Open (was: Closed)
https://pagure.io/fedora-ci/general/issue/23 is fixed, yet still no link in:
https://src.fedoraproject.org/rpms/python3/pull-request/85
(That link should say "pending" now. I'll update this after the CI job finishes.)
@churchyard pending state is tracked in https://pagure.io/fedora-ci/general/issue/3
The job finished and the link is shown. I confirm this as fixed. Thanks.
Login to comment on this ticket.