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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Build fails with "No failed test found. A possible compilation error occured" on script task


Just trying to move to Bamboo from TeamCity.  This is my first small task.

I use a Script Task to compile my GoogleTest C++ code which has some intentional code that causes warnings in the compile (think passing null pointers to test how it is handled).

All my tests pass, but the overall build fails due to the compilation warnings stated above.

My question is if there is anyway to have bamboo ignore these warnings? I do not want to turn off the warnings in my compile as this could cloak problems in non-test code.

If it makes a difference, my build agent is running on a RHEL7 virtual machine.

1 answer

1 accepted

0 votes
Answer accepted

Never mind.  The build was failing due to an artifact not being created with the proper name.  Was at the end of the log and I was fixated on compile warnings.

Hi Michael Moore,

We are getting this kind of error "No failed test found. A possible compilation error occurred." in Bamboo build logs...?

Why bamboo is not properly parse the build logs..?


It has been a long time, but we had misspelled an artifact (product RPM) and it wasn't finding the one it was looking for so tests didn't run.

I'm afraid I don't remember anything more specific.



Like likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events