We have a pipeline that runs an exceptional test which is expected to take a few hours.
The step is executed as a Docker compose command using a BitBucket Docker sevice container.
Now the pipeline logs report that the Docker compose command has ended after approx. 4.5 hours. There is also no more output after that time.
But we expect the test run to not be completed. In the metrics we see indeed that there is still a lot of CPU usage after the 1.5h mark.
Also the pipeline reports to have succesfully ended after approx. 5 hours (which is more the time we would have expected). So there is a time frame of appprox. 3 hours were the pipeline still continues, but we have no output nor any other progress report.
We have also set the time limit of the step to the maximum of 720 minutes
Now is my question: why is my step marked as ended after 1.5 hours when it has clearly continued for a few more hours.
