Possible bug: cancelling last job while it was waiting for an agent doesn't finish a build

[tomdeboer]

Hi there,

In our environment, we often find ourselves cancelling steps that are waiting for an agent, if we know the agent is not going to be available soon. In this case we manually cancel this step and this is OK.

What we often see, however, is that if we cancel the last step of a build that was waiting for an agent, the build itself will just hang and never finish, as if it was still waiting for steps to finish. Only clicking cancel on the "build level" will finally stop the build itself.

I assume this is a bug?

Reproducing is relatively easy.

• Create a pipeline with more than one step, and use the agent: property to assign one job to an agent that doesn't exist.
• Start the pipeline and let the first step finish. The second job will wait forever and not finish.
• Cancel the second step while it is waiting

You may observe the build doesn't actually finish, even though all steps have completed.

• Tom

[ticky]

Hi Tom, thanks for the report. This is a bug we've been working to track down, if you send a link to the stuck build to support@buildkite.com we can resolve the state in the interim.