Expected Behavior
Once Cirrus job is done, GitHub displays it as finished.
Real Behavior
Even though Cirrus completed the job, GitHub still lists it as not-even-started-yet.
Related Info
This is a (tick one of the following): not sure what to tick because this feels like an API issue
The most recent occurrence is here: newsboat/newsboat#3084 Interesting details:
- Cirrus started a job when I pushed the branch, then started a new one when I immediately made a PR
- most of the "stuck" jobs have a rule that they shouldn't run in this case (the PR updates translation, so compilation checks are skipped)
Expected Behavior
Once Cirrus job is done, GitHub displays it as finished.
Real Behavior
Even though Cirrus completed the job, GitHub still lists it as not-even-started-yet.
Related Info
This is a (tick one of the following): not sure what to tick because this feels like an API issue
The most recent occurrence is here: newsboat/newsboat#3084 Interesting details: