CI run report is left lingering after broker restarts
I noticed that I have one repository which has a job which is left in running state. It has its src/ tree checked out but no report generated, and other runs have already happened. I suspect this happened because the cib process was restarted in the middle of a run, but not 100% sure.
See discussion on zulip
From Zulip:
I'm thinking that a fix for this is that when cib starts, it looks for any run that isn't in the finished state and marks it as failed.