Windows-runner step fails sometimes and shows no log-data

[Dominik Bregovic]

Hallo Community,

In my company we are using Bitbucket pipelines and most of the time they work fine.

But i have a problem with a pipeline that uses this image:

"image: mcr.microsoft.com/dotnet/sdk:6.0 + Windows-runners"

Step1:

In this step i log into Azure and start a VM. (always successfull).

After the VM starts it logs in automatically, starts the runnerscript on Auto-start and connects the VM with Bitbucket. This works also (always successfull).

Here i have added a delay time with "sleep 300" in order to give the VM enought time to do it's thing.

Step2: 

In the next step i want to execute a build-script which i call over the pipeline and here things sometimes break.

Sometimes the initial "Build setup" doesn't execute properly and therefor my script can't even be called. 

On average it workes 4 out of 5 times. This number is not consistent. 

I will insert a screenshot where my pipeline fails here:

Here the last screenshot of the unconsistent system error:

Best 

Dominik Bregovic

[Dominik Bregovic]

.

[Theodora Boudale]

Hi Dominik,

1) Does the virtual machine where the runner is running meet the minimum requirements listed here for Windows?

• https://support.atlassian.com/bitbucket-cloud/docs/runners/#Minimum-Requirements

With regards to the memory requirement, please note that more than 8GB will be needed if you are running steps with 4x or 8x size.

2) Can you check the log file of the runner, find the entries for the date and time that such a failed build was executed and post them here? (Please make sure to sanitize any private data in the logs prior to sharing).

The runner log file is located at:

atlassian-bitbucket-pipelines-runner\temp\b609961f-891e-c872-c36b-f3f2c315d186\runner.log

where

• atlassian-bitbucket-pipelines-runner is the directory where you unzipped the runner zip
• b609961f-891e-c872-c36b-f3f2c315d186 is an example runner uuid, there should be a directory with the uuid of your runner in atlassian-bitbucket-pipelines-runner\temp

If your repos belong to a workspace on a paid billing plan, you can also create a support ticket if you prefer to share the logs privately (a support ticket will be visible only to you and Atlassian staff). You can create a ticket via https://support.atlassian.com/contact/#/, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product.

Kind regards,
Theodora

[Dominik Bregovic]

Hello Theodora,

1. First to the requirements:

From my point of view it should work out because we do not have any 4x or 8x step sizes, but i will paste the system details of the VM in here:

I hope you are able to zoom in, if not here is the another picture of the System Ram:

2. Now to the log data: 

On Bitbucket i was able to see that the error occured on the 12th of Jannuary at 06:08:10 pm, which this picture shows:

In the path:

atlassian-bitbucket-pipelines-runner\temp\d134924d-3bb5-542a-961c-16f929e16016\runner.2023-01-12.0.log

I am not able to see any log data after 2023-01-12 17:20:59 like this picture shows:

The whole log was sent to the support like you suggested.

Best

Dominik

[Theodora Boudale]

Hi Dominik,

Since you created a support ticket, it's best to focus on that, in order to avoid any confusion that may arise from troubleshooting the problem in two different places with two different people. Please make sure to provide the URL for some of these failed builds as well in the support ticket, so that my colleague who will work on your ticket can check additional logs from our side.

Kind regards,
Theodora