Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,462,882
Community Members
 
Community Events
176
Community Groups

Where are the rest of the console logs?

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?

1 answer

0 votes

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:

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

I spent almost four hours trying to make this work, and I conclude that it is unrealistic. We have a complex pipeline that requires significant context to run. Normally this context is setup by a custom docker container and 8 internal pipeline steps.  I was able to mostly recreate the context but I ran out of time.

 

What I want is simply to get the console logs from the application under test. I think they should be kept somewhere automatically.  At most, some configuration flag should be set to make these logs available.  Requiring a completely different execution environment is a significant negative feature of BB pipelines.

Hi Mark,

I understand that the process of debugging this locally has been time-consuming.

I have created a ticket with the support team to investigate this issue further. You should have received an email with a link to the support ticket. Just in case you haven't received it, please feel free to let me know and I can post the ticket URL here. The ticket will be visible only to you and Atlassian staff, no one else can view its contents even if they have the URL.


I would like to ask if you could please leave a reply in the support ticket and provide:

  • The URL of a Pipelines build with failed tests where you are missing the console log.
    Please also mention what command from your script you expect to show the console logs.
  • We would need to know what console output you are missing, so it would be useful if you could provide the output you get when you run the same tests in your local development environment, so we can compare.

If you have any questions, please feel free to let me know.

Kind regards,
Theodora

Here is the <url_removed> with failed tests.  Check the integration tests section and notice this error:

"org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [select distinct SPECIES_NAME from ANIMAL_PROTOCOL_ITEMS where TENANTID = '8f9cdc53-2d86-426f-85e0-37151b982a72' order by SPECIES_NAME ASC]; nested exception is net.snowflake.client.jdbc.SnowflakeSQLException: SQL compilation error:Object 'ANIMAL_PROTOCOL_ITEMS' does not exist or not authorized."

Since the SQL is known to be good (it is very simple and works in local testing), the likely problem is that the URL, userid, and password for the JDBC access are not available in the integration test environment. These values are passed to the code via environment variables from repository settings. This error does not occur in local testing, where the environment variables are set locally.

The code always prints the URL with this statement; the userid and password are not printed:

log.info("DARE/Snowflake url is {}", url);

If I could see this message in the console log, I could easily verify whether the environment variables that are set via the repository settings are coming through to the integration tests in the pipeline.

Hi Mark,

Thank you for the info.

I have added this along with the URL of the build in the support ticket I created for you, so that the engineer that will be working on your ticket can check.

Just a heads up, I removed the URL of your build from your post to protect your privacy.

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events