Problem to solve
I’ve been running pipelines in gitlab CI/CD to check linting, for months.
Yesterday multiple of these linting jobs never finished running, even though the “Job succeeded” was printed to logs.
Ended up running a zombi job for 89 minutes, until it depleted all minutes and stopped, before I could notice. Now I can’t run my pipelines anymore.
- What are you seeing, and how does that differ from what you expect to see?
- Until now that very same job would succeed and stop, showing it as complete.
- Consider including screenshots, error messages, and/or other helpful visuals
In the screenshot you can see the job was canceled at last, after 84 minutes running. Meanwhile the logs show “Job succeeded”.
Steps to reproduce
Which troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?
Bit lacking on this section, simply because I would have no idea where to start from. Besides, my minutes are depleted and I would like them refunded, any chance I can get them back and troubleshoot further?
Configuration
Add the CI/CD configuration from .gitlab-ci.yml and other configuration if relevant (e.g. docker-compose.yml). Alternatively, create a public GitLab.com example project that provides all necessary files to reproduce the question.
Versions
Please select whether options apply, and add the version information.
- Self-managed
- GitLab.com SaaS (this is GitLab’s default runners right?)
- Self-hosted Runners
