Bamboo JUnit test parser fails to find test results

If I have a build running on the same instance it was running before, Bamboo fails to find (or recognize) the unit test results. I have tested that the test results exists (with a simple Script step doing ls -l right befire the JUnit test parser is called).

If I terminate the Bamboo agent Elastic instance and run the same plan again, JUnit test parser finds the test restults.

May be relevant: I am using Gradle

2 answers

1 accepted

Accepted Answer
1 vote

Hi Aleksey,

You seem to be experiencing this bug: The workaround for which at the moment is using a 'touch' command right before the JUnit task and maybe adding "sleep 5;" before the 'touch' command. (Please check this page as well:

Side Note: In cases that test results are somewhat produced from a script task that uses operations like copy or move, you should place the xml file in the repository for it to be checkout to your working directory and then use the parser directly.

Hope this helps!



As a workaround I have set an option to run builds on clean working directory. But would love to have a better solution.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Jira Ops

Jira Ops Early Access Program Update #2: Let’s talk severity levels

Welcome to your weekly Jira Ops Early access program update, where we’re sharing news and updates on Jira Ops' progress as we work toward our 1.0 release. If you ever want to drop us feedback or idea...

31 views 0 0
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you