Home → Questions →

Failed job is cancelled but keeps running

• Edit

dane

19 Nov, 2014 01:22 AM

Seeing a case where a project with two matrix runs had one fail. Then I cancelled the build so the other would not run. The job is marked as "cancelling" but appears to keep on running and the other is still queued. https://ci.appveyor.com/project/Mapbox/mapbox-studio/build/1.0.1504

Any ideas for how to get these jobs unstuck?

1. Support Staff 1 Posted by Feodor Fitsner on 19 Nov, 2014 01:25 AM

   

   Something is going on Azure right now. I'm looking into that.

   • Edit

2. 2 Posted by dane on 19 Nov, 2014 02:14 AM

   

   Okay, thank you.

   Dane

   • Edit

3. Support Staff 3 Posted by Feodor Fitsner on 19 Nov, 2014 05:17 AM

   

   It's getting back.

   • Edit

4. 4 Posted by dane on 19 Nov, 2014 06:31 PM

   

   All good now. I still had backed up jobs that started within the last few hours, but cancelling them all and pushing new commits now fixed things. One suggestion: the list of previous jobs on a page like https://ci.appveyor.com/project/Mapbox/mapbox-studio/history is limited to the last 10 jobs. In my case I had stuck jobs that needed cancelled that were not visible. I worked around this by going to the projects view (https://ci.appveyor.com/projects) where the still running/stuck jobs did show up and I could cancel them there. My suggestion would be to have the history page to at least the last 20 jobs, or maybe the last N jobs + at the bottom the first jobs in the queue still running. That way you could cancel the first, refesh the page, and eventually be able to nuke them all.

   • Edit

5. Support Staff 5 Posted by Feodor Fitsner on 19 Nov, 2014 06:33 PM

   

   There is ellipsis button at the bottom of the list loading more records.

   • Edit

6. 6 Posted by dane on 19 Nov, 2014 11:51 PM

   

   Aha! Thanks, I would have never noticed that without the hint.

   • Edit

7. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:50 AM.