I am running a test case based on gtest, which can take up-to 6 minutes without any stdout. This runs well locally, but in pipelines, after ~30 sec, it behaves like a shutdown signal was received. If this is the expected behavior, is there a workaround?
Hi Awsin,
Pipelines doesn't automatically shutdown if there is no log output.
Are you able to post an example of your bitbucket-pipelines.yml configuration?
You could also add a background tasks to collect process information, by following the instructions here: https://confluence.atlassian.com/bitbucket/how-to-generate-support-logs-in-your-pipeline-959288939.html
That might reveal a hung process or something.
Thanks,
Phil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.