Where are the rest of the console logs?

Mark Linehan_c84fj9

Our builds run a BB pipeline that includes steps for unit and integration testing.  If a test fails, we get a very nice report showing the failure.  What's missing is the console log showing output from the application before the code hit the assert() that triggered the test failure.  We need that previous output to diagnose the problem.

We have some tests that work fine when running in a local development environment, where we can see the console output and also use a debugger.

For tests that fail only in the build pipeline, obviously we can't use a debugger so the only option is to get hints printed out to tell us what is going on.  But we can't find that console output.  Where should we look?

Theodora Boudale

Hi @Mark Linehan and welcome to the community.

I would suggest debugging this locally with Docker and seeing if you get the same output as in the Pipelines build or not.

This would help narrow down whether the issue seems to be specific to Pipelines or not (e.g. it could be related to some configuration that you have in your local environment that doesn't exist in the Docker image you use).

The steps to debug this locally are the following:

1. Take a new clone of the repo on your machine (don't use an existing one)

2. Navigate to the directory of that new clone, and do a git reset --hard to the commit of a failed build with this issue

3. Afterwards, start a Docker container with the following command

docker run -it --volume=/Users/myUserName/code/my-repo:/localDebugRepo --workdir="/localDebugRepo" --memory=4g --memory-swap=4g --memory-swappiness=0 --cpus=4 --entrypoint=/bin/bash atlassian/default-image:3

Replace /Users/myUserName/code/my-repo in the command with the path of the clone you took on step 1.

Replace atlassian/default-image:3 in the command with the Docker image you are using in bitbucket-pipelines.yml for the step of the failed build.

In case your build uses services, you can check the documentation below on how to use services to test locally:

• https://support.atlassian.com/bitbucket-cloud/docs/debug-pipelines-locally-with-docker/#Testing-with-build-services

4. After the Docker container starts, you are inside your working directory and you can start executing commands.

You can run individual commands from your bitbucket-pipelines.yml and check if you see the output that is missing from the Pipelines log or not.

You can also configure tools inside the container.

Please feel free to let me know how it goes and if you have any questions.

Kind regards,
Theodora