It looks like there is some network issue on jenkins-continuous-infra.apps.ci.centos.org that is causing Fedora CI jobs to run much slower than usual.
For example the triggers job should take just a few seconds and not minutes to run.
https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/job/fedora-build-pipeline-trigger/328091/ https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/job/fedora-build-pipeline-trigger/328090/ https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/job/fedora-build-pipeline-trigger/328089/
This build job also seems to have been impacted due to the issue: https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/job/fedora-f30-build-pipeline/685/console
This ticket is related to https://pagure.io/fedora-ci/general/issue/61
Metadata Update from @bstinson: - Issue assigned to bstinson
Not sure what changed, but seems are much quicker now: - https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/job/fedora-f30-build-pipeline/688/ took 45 minutes - https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/job/fedora-f30-build-pipeline/692/ is back to less than 8 minutes
So from a symptom perspective this seems to be fine but I do not know the cause for it :)
I'm actively working on this right now which is why you're seeing wildly different numbers.
Basically the scheduler decided to put everything on 1 physical node (the jenkins master, STR VMs, etc)
Ok, I think we're in better shape now. The main cause was the scheduler crowding one of our nodes. In the future we'll add some tags that will manage this a little bit better, but for now I pinned the jenkins master in another place.
Metadata Update from @bstinson: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.