-
Notifications
You must be signed in to change notification settings - Fork 973
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Completed jobs still hanging in the UI #12714
Comments
Similar to #12762 you need to include a precise set of steps that you are performing that creates this problem. You haven’t followed up there with the sequence of events that you are triggering so I’m not so confident we are going to get anywhere here either. There’s not much value in creating new issues if you’re not following up with the requested information on the ones you already created. This error implies something very wrong is happening, such as deleting dependencies or parts of pipelines while they are still running, or something like that. Please share more details on how to reproduce the error or more details in what you are doing with these pipelines, or there’s likely nothing that can be done here. |
Sorry, missed the steps to reproduce. All of these pipelines were not triggered via the API, they are manually triggered in the UI (eg.: consul-alerts) or triggered by a change in the git repository (eg: tech-docs). These hanging errors weren't happening with the 19.12v. |
Hello Chad, I apologise for the long delay in following up with the issues I've opened. I would like to ask you which different details are missing for this issue in order to proceed with the investigation to fix it. The pipelines are still hanging in the UI. As mentioned, all of them were triggered via UI or automatically triggered via a git merge. The errors are still in the log with the same exception in the JobStatusListener. Please, let me know which pieces of information are missing to track the issue. |
Issue Type
Summary
Pipelines that aren't triggered via the API are complete but still showing as hanging in the UI
Environment
Basic environment details
23.5.0 (18179-7702b283accd1f90f014f0087aa2e9bd8baf4a97)
17.0.9
Linux 4.19.0-23-cloud-amd64
Additional Environment Details
Steps to Reproduce
Expected Results
I would expect the pipeline to report completed and not as not responding in the UI
Actual Results
Pipeline is completed and successful but reported as not responding in the UI
Possible Fix
Log snippets
Code snippets/Screenshots
Any other info
The text was updated successfully, but these errors were encountered: