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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Build fails with with error "Process 'Gradle Test Executor' finished with non-zero exit value 255"


Ever since Friday, our builds have been failing on Bamboo with the following error:

24-Apr-2020 12:28:33 FAILURE: Build failed with an exception.
24-Apr-2020 12:28:33
24-Apr-2020 12:28:33 * What went wrong:
24-Apr-2020 12:28:33 Execution failed for task ':knight:test'.
24-Apr-2020 12:28:33 > Process 'Gradle Test Executor 2' finished with non-zero exit value 255
24-Apr-2020 12:28:33 This problem might be caused by incorrect test process configuration.
24-Apr-2020 12:28:33 Please refer to the test execution section in the User Manual at
24-Apr-2020 12:28:33
24-Apr-2020 12:28:33 * Try:
24-Apr-2020 12:28:33 Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
24-Apr-2020 12:28:33
24-Apr-2020 12:28:33 * Get more help at

However, absolutely nothing changed in the project since then. Running a build that passed before now fails. How can this happen?

Our only guess at this point is that something went wrong with the Bamboo configuration. We did some changes on Friday, including switching some projects to JDK 11, but reverted them after some branches started failing.

One branch still works, but we can't figure out what's different. We already tried switching the JDK versions back and forth, but so far without any success.

Could something external have changed then? In our build.gradle we use only versioned dependencies, so I don't think that could be the issue. But at this point, I don't really have any ideas what could be going wrong.

Any ideas or help would be greatly appreciated.

1 answer

1 accepted

0 votes
Answer accepted

We managed to get it to work again by changing the actual build step from:

./gradlew clean build -d


./gradlew clean build -d
./gradlew --stop

However, this still does not explain why it was working up until Friday. Any ideas?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events