Pipeline stuck in `running` state
Summary
One of our pipelines are stuck in the running state, even though all jobs have completed.
Steps to reproduce
Not sure how to reproduce, have only seen it happen to one pipeline.
Relevant logs and/or screenshots
This is on gitlab.com, at kada-development/konvent-web/pipelines/6742367
Output of checks
This bug happens on GitLab.com
Activity
Strange. It looks like it's been stuck like that for 2 weeks.
@godfat Have you seen this before?
@markglenfletcher If it's a few minutes or even hours, it could be that the system was overloaded, and we'll need to wait for the queue. But 2 weeks sounds forever, it could be that the job didn't get processed properly, and was dropped eventually. If this is not happening often, then I won't worry about it.
As for why it's out synchronized, please see https://gitlab.com/gitlab-org/gitlab-ce/issues/23257
mentioned in issue #1622 (closed)
Reported here #1643
Now I think this is https://gitlab.com/gitlab-com/support-forum/issues/1622 and we're trying to fix it at https://gitlab.com/gitlab-com/infrastructure/issues/1441
mentioned in issue #1666
