Issue Summary

If a Pipelines build is still running in the background and it hit the max build time limit (e.g. using max-time config), the total time it takes to run the script doesn't match the total step execution time.

Steps to Reproduce

In a repository with Pipelines enabled, copy the configuration below and run a Pipeline build

• • image: atlassian/default-image:2
    
    pipelines:
      default:
        - step:
            name: 'Test'
            max-time: 2
            script:
              - sleep 5m
              - echo "done"
    

Expected Results

The scripts/commands total time are matched with the total step execution time

Actual Results

The scripts/commands total time are not matched with the total step execution time

Result:

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available