Build has hit timeout limit

CircleCI has a built-in 10 minute no-output timeout. This means that if it has been 10 minutes since the last output, the build will be cancelled and stopped. This can cause users to encounter issues where they intend for a part of their build to continue beyond 10 minutes without giving output, but the system kills it.

The no_output_timeout parameter for run gives users the option to change the no-output timeout from the default 10 minutes to a user-specified timeout.

For example, if we have a run step as follows:

- run:
    command: . ./

If we expect our script will take a while to complete execution, we can extend the no-output timeout as follows:

- run:  
    command: . ./
    no_output_timout: 30m

The value set for no_output_timeout can be in hours, minutes or seconds - a digit followed by h, m or s respectively. Partial times can also be used, like 1.5h.

Was this article helpful?
0 out of 0 found this helpful



Article is closed for comments.