# Job is not terminated at node run time error

**URL:** <https://forum.buildkite.community/t/job-is-not-terminated-at-node-run-time-error/531>\
**Category:** General\
**Created:** [May 30, 2019, 10:41pm UTC](https://forum.buildkite.community/t/job-is-not-terminated-at-node-run-time-error/531 "2019-05-30T22:41:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![zhex900](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/zhex900/32/559_2.png) [@zhex900](https://forum.buildkite.community/u/zhex900)\
**Post date:** [May 30, 2019, 10:41pm UTC](https://forum.buildkite.community/t/job-is-not-terminated-at-node-run-time-error/531/1 "2019-05-30T22:41:39Z")

</div>

Hi,

My job had a run time error. I expect the job should terminate and mark at it as a failure. But it keeps running (yellow). Is there a way to fix this.

```
    RangeError: Maximum call stack size exceeded

at _hasBinary (/var/lib/buildkite-agent/.cache/Cypress/3.3.1/Cypress/resources/app/packages/socket/node_modules/has-binary/index.js:25:22)

at _hasBinary (/var/lib/buildkite-agent/.cache/Cypress/3.3.1/Cypress/resources/app/packages/socket/node_modules/has-binary/index.js:49:63)

at /var/lib/buildkite-agent/.cache/Cypress/3.3.1/Cypress/resources/app/packages/socket/node_modules/socket.io/lib/socket.js:369:16

at /var/lib/buildkite-agent/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/lib/socket.js:308:22

at tryCatcher (/var/lib/buildkite-agent/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/node_modules/bluebird/js/release/util.js:16:23)

at Promise._settlePromiseFromHandler (/var/lib/buildkite-agent/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/node_modules/bluebird/js/release/promise.js:510:31)

at Promise._settlePromise (/var/lib/buildkite-agent/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/node_modules/bluebird/js/release/promise.js:567:18)

at Promise._settlePromise0 (/var/lib/buildkite-agent/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/node_modules/bluebird/js/release/promise.js:612:10)

at Promise._settlePromises (/var/lib/buildkite-agent/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/node_modules/bluebird/js/release/promise.js:687:18)

at Async._drainQueue (/var/lib/buildkite-agent/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/node_modules/bluebird/js/release/async.js:133:16)

at Async._drainQueues (/var/lib/buildkite-agent/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/node_modules/bluebird/js/release/async.js:143:10)

at Immediate.Async.drainQueues (/var/lib/buildkite-agent/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/node_modules/bluebird/js/release/async.js:17:14)

at runCallback (timers.js:789:20)

at tryOnImmediate (timers.js:751:5)

at processImmediate [as _immediateCallback] (timers.js:722:5)

```

---

<div class="post-metadata">

**Author:** ![anon46008679](https://avatars.discourse-cdn.com/v4/letter/a/da6949/32.png) [@anon46008679](https://forum.buildkite.community/u/anon46008679)\
**Post date:** [May 30, 2019, 11:34pm UTC](https://forum.buildkite.community/t/job-is-not-terminated-at-node-run-time-error/531/2 "2019-05-30T23:34:36Z")

</div>

It looks like maybe your scripts/commands are stuck, and not existing properly?

If your command isn’t timing out itself, or exiting properly, you can add a `timeout_in_minutes` on the step and Buildkite will force it to exit and finish regardless of if it’s stuck:

> **[Command Steps](https://buildkite.com/docs/pipelines/command-step#command-step-attributes)**
>
> Automate your team’s software development processes, from testing through to delivery, no matter the language, environment or toolchain.