You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi,
I am running a self host runner on Windows and I am having this issue:
[2022-08-03 17:08:54,077] Updating runner state to "ONLINE".
[2022-08-03 17:09:02,746] Setting runner state to executing step.
[2022-08-03 17:09:02,756] Getting step StepId{IHaveDeletedItForSecurityPurposes}
[2022-08-03 17:09:02,766] Getting oauth token for step.
[2022-08-03 17:09:02,769] Getting environment variables for step.
[2022-08-03 17:09:03,151] Getting all artifacts for step.
[2022-08-03 17:09:03,353] Setting up directories.
[2022-08-03 17:09:03,355] Starting log uploader.
[2022-08-03 17:09:03,358] Setting up step timeout: PT2H
[2022-08-03 17:09:03,365] Starting websocket listening to STEP_COMPLETED events.
[2022-08-03 17:09:03,366] Checking for step completion every PT30S seconds.
[2022-08-03 17:09:03,561] Updating step progress to CLONING.
[2022-08-03 17:09:03,875] Generating clone script.
[2022-08-03 17:09:03,891] Adding log file: C:\Users\LUC\source\repos\atlassian-bitbucket-pipelines-runner\bin\..\temp\b64bab56-8f78-5112-aacb-60e5b7e2be6a\1659541352857\tmp\clone14940335475468784215.log
[2022-08-03 17:09:03,892] Executing clone script.
[2022-08-03 17:09:04,376] Appending log line to main log.
[2022-08-03 17:09:10,624] Script exited with exit code: 1
[2022-08-03 17:09:10,634] Not uploading caches. (numberOfCaches: 0, resultOrError: ERROR)
[2022-08-03 17:09:10,636] Not uploading artifacts. (numberOfArtifacts: 0, resultOrError: ERROR)
[2022-08-03 17:09:10,636] Updating step progress to PARSING_TEST_RESULTS.
[2022-08-03 17:09:10,899] Test report processing complete.
[2022-08-03 17:09:10,905] Updating step progress to COMPLETING_LOGS.
[2022-08-03 17:09:11,137] Shutting down log uploader.
[2022-08-03 17:09:11,140] Appending log line to main log.
[2022-08-03 17:09:11,475] Tearing down directories.
[2022-08-03 17:09:11,723] Cancelling timeout
[2022-08-03 17:09:11,727] Completing step with result Result{status=ERROR, error=Some(Error{key='runner.bitbucket-pipelines.clone-failure', message='We couldn't clone the repository. Try rerunning the pipeline.', arguments={}})}.
[2022-08-03 17:09:11,969] Setting runner state to not executing step.
[2022-08-03 17:09:11,971] Waiting for next step.
[2022-08-03 17:09:24,076] Updating runner state to "ONLINE".
I saw a similar thread but it is for docker, thus I am raising it as a new issue.
This is my yml file:
image: mcr.microsoft.com/dotnet/core/sdk:3.1
pipelines:
default:
- step:
runs-on:
- self.hosted
- windows
name: build and run
# caches:
# - dotnetcore
script:
- export SOLUTION_NAME=AutomationSolution
- export CONFIGURATION=Release
- export REPORTS_REL_PATH=./test-reports/build_${BITBUCKET_BUILD_NUMBER}
- export REPORTS_PATH=./${PROJECT_NAME}/test-reports/build_${BITBUCKET_BUILD_NUMBER}
- dotnet restore $SOLUTION_NAME.sln
- dotnet build --no-restore $SOLUTION_NAME.sln --configuration $CONFIGURATION
- export
- dotnet test --no-build $SOLUTION_NAME.sln --test-adapter-path:. --logger:"junit;LogFilePath=$REPORTS_REL_PATH/junit.xml"
Could you please advice?
Thank you,
Luis
Hi Luis,
Could you please
This section shows, among other things, the output of the clone command, and it may give us an indication of why the clone is failing.
Could you also let us know what version of the Windows runner you are using?
Kind regards,
Theodora
Hi @Theodora Boudale ,
This is the Build Setup:
+ $env:GIT_LFS_SKIP_SMUDGE = '1'; git clone --branch='Luis-Castro/bitbucketpipelinesyml-edited-online-with-1658159320916' --depth 50 "https://x-token-auth:$Env:REPOSITORY_OAUTH_ACCESS_TOKEN@bitbucket.org/$env:BITBUCKET_REPO_FULL_NAME.git" $env:BUILD_DIR
Cloning into 'C:\Users\LUC\source\repos\atlassian-bitbucket-pipelines-runner\bin\..\temp\b64bab56-8f78-5112-aacb-60e5b7e2be6a\1659541352857\build'...
And the version is: 1.343
Thanks,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Luis,
Apologies for the late reply, there must have been a glitch in our system as I got no notification for your earlier reply.
I don't see any useful info in the output of the clone command.
I would like to ask for some additional info so we can further investigate.
1. Could you please provide the content of the file
C:\Users\LUC\source\repos\atlassian-bitbucket-pipelines-runner\bin\..\temp\b64bab56-8f78-5112-aacb-60e5b7e2be6a\1659541352857\tmp\clone14940335475468784215.log
This path is mentioned in the output you provided in your original question
2. Could you please provide the "runner.log" file from your Windows Runner (just the entries at the date and time of that build)
3. Is this a workspace or a repository runner?
4. Was this runner working previously for this repo and then it started failing on 3rd August? Or has it always been failing for this repo?
5. In case this is a workspace runner and if you are using it for multiple repos, does the clone in builds of other repos succeed?
6. Are the prerequisites mentioned in the following page met for the Windows server where you run the runner?
https://support.atlassian.com/bitbucket-cloud/docs/set-up-runners-for-windows/
Kind regards,
Theodora
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.