When does a build minute start counting?

[Dennis Thisner]

I am reading the FAQ and I found this:

```What is a build minute?

Build minutes are minutes executing a pipeline on a runner, excluding time acquiring a runner. In other words, they're the minutes when your pipeline status is "In progress".```

What I am still not understanding is, when does it start counting?

I have a project where it says it timeout because it "

Exceeded build time limit of 120 minutes."

I am looking at my logs and first section took 4min
The second section took 119m 59s.
But, when I take a closer look, this is what it is showing and it is showing close to 2.5min

So, my questions is: When does the so called "Build Time" actually start?
Is it when it is waiting for a runner?
Is it when it is "In Progress"?

[Tom Bradshaw]

Hi @Dennis Thisner,

The build time starts when you start pulling the docker image you specify in your bitbucket-pipelines.yml. The build time stops when the build container terminates. Normally this happens when the final command in the build runs but it looks like in your case this is not happening.

Without seeing more of your build I can't be certain for sure but it sounds like your build contains a process that did not terminate after the final command. When this happens the build container can't terminate and the step can't complete. In this case the build effectively hangs until the timeout occurs. To debug this problem I recommend running

while true; do ps -aux && sleep 30; done &

as the first command in your build. This will display all processes running in the build every 30 seconds and allow you to find the unterminated process. You can then start looking for why this process is not being terminated along with the previous step.

Cheers,

Tom.

[Dennis Thisner]

awesome! thanks Thomas :)