Test Analytics plugin keeps failing

Test Analytics
1

I have a step which converts my reports into a JUnit report and uploads the artifacts. This step is then followed by another step which uses the test collector which is in charge of the test analytics. This last step keeps to failing.

Ex code:

- label: ":hammer_and_pick: Generate JUnit Report"
   key: "createJUnitReport"
   commands:
     - "mkdir -p ./build"
     - "buildkite-agent artifact download 'build/karate-report.tar.gz' ./build"
     - "tar -xzf build/karate-report.tar.gz -C ./build"
     - "./gradlew convertKarateToJUnit"
   env:
     JDK_RPM_VERSION: 17
     DEPLOY_ENV: ${DEPLOY_ENV:-qa}
   agents:
     queue: java17:0.1.6
   artifact_paths:
     - "build/test-results/karateTest/TEST-karateTest.xml"

 - wait

 - label: ":test-analytics: Test Analytics"
   command:
     - "buildkite-agent artifact download 'build/test-results/karateTest/TEST-karateTest.xml' ."
   plugins:
     - test-collector#v1.10.2:
         files: "build/test-results/karateTest/TEST-karateTest.xml"
         format: "junit"

Error:

Running plugin test-collector pre-exit hook
# Enabling output redaction for values from environment variables matching: [*_PASSWORD *_SECRET *_TOKEN *_PRIVATE_KEY *_ACCESS_KEY *_SECRET_KEY *_CONNECTION_STRING]
# A hook runner was written to "/tmp/buildkite-agent-hook-wrapper/hook-script-wrapper-1930665351" with the following:
$ /tmp/buildkite-agent-hook-wrapper/hook-script-wrapper-1930665351
# ↳ Command completed in 17.439µs
🚨 Error: Error tearing down job executor: error running "/tmp/buildkite-agent-hook-wrapper/hook-script-wrapper-1930665351": Process working directory "/buildkite/builds/IA-[spoiler]This text will be blurred[/spoiler]" doesn't exist

Any idea what I am doing wrong?

2

Hey @svasco,

It seems the error may be due to the directory structure or files not matching what’s expected when the step runs.

In the Generate JUnit step, please verify if the artifact was successfully uploaded and the exact folder it was uploaded to. You can add a pwd in the upload step and an ls in the download step to ensure the paths match.

If you’re still facing issues, feel free to email us at support@buildkite.com with a link to your build, and we can take a closer look.