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?
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.
...hey are a part of us, shaping how we interact with the world around us. The same holds true for programming languages when we think about how different kinds of vulnerabilities raise their heads in t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events