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

[Michael Moore]

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.

[Michael Moore · Accepted solution]

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.

[nithyananthaml@hcl.com]

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..?

[Michael Moore]

Hey,

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.

Mike