Job being killed on MacOS

Hi, how are you ?

I’m having a problem on a on-premise build using MacOS where a job receives a cancelation signal at random times (cloning, running a plugin or the commands of a step).

This occurs on a matrix build, where the first step finishes successfuly and the second one always receives the cancelation signal (other items of the matrix don’t even start and show a “Canceled” status).

Example logs from my pipeline:

... <Build commands outputting as normal>...
# Received cancellation signal, interrupting
🚨 Error: The command was interrupted by a signal: signal: terminated

Logs from the agent:

Finished job xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (Previous job of the matrix)
Assigned job yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy. Accepting... (step that receives the signal)
Starting job yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy
[Process] Process is running with PID: 63633
Canceling job yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy with a grace period of 10s
Process with PID: 63633 finished with Exit Status: 255, Signal: nil
Finished job yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy
Assigned job zzzzzzzz-zzzz-zzzz-zzzz-zzzzzzzzzzzz. Accepting... (another step in my pipeline)

System information:
Agent: buildkite-agent version 3.73.1+8506.d2135456fb5cedeb6c8c982fdb428de5d02c7cf9
System Version: macOS 13.6 (22G120)
Kernel Version: Darwin 22.6.0

Nothing seems to kill the related PID (dmesg wise at least). What could be causing this weird behavior?

Edit: Changed the post to General instead of Pipeline, sorry.

Hello @flavioarieta,

We’ll need to take a closer look at the pipeline where you see this happening. Could you please email links to a couple of builds illustrating the problematic behaviour

Additionally, could you please share the agent configuration, any hooks or plugins you might be using, as well as, system logs around the time of the occurrence(s) of this issue?

Hi! Thank you for the reply.

I’ll send you guys a email regarding the issue with the informations.

Thank you.