TeamCity Build Log messed up with "Cannot find Latest successful build"
Answered
Hello,
I added a new (legacy) project to TeamCity and my Build Log is messed up with "Cannot find Latest successful build" messages like the lines below.
My build log file has 15280 lines and 3140 of them start with "Cannot find Latest successful build". The Build Process is also very slow on the build server (longer than 30 minutes). It takes only some seconds to build the project on my developer PC.
Any ideas how to fix this?
Best regards!
Stefan
[18:50:42]W: Cannot find Latest successful build, branch: 'feature/MM-51-update-der-unittests' to calculate metric 'number of failed tests' for branch feature/MM-51-update-der-unittests
[18:50:42]W: Cannot find Latest successful build to calculate metric 'number of failed tests'
[18:50:42]W: Cannot find Latest successful build, branch: 'feature/MM-51-update-der-unittests' to calculate metric 'number of inspection errors' for branch feature/MM-51-update-der-unittests
[18:50:42]W: Cannot find Latest successful build to calculate metric 'number of inspection errors'
[18:50:42]W: Cannot find Latest successful build, branch: 'feature/MM-51-update-der-unittests' to calculate metric 'number of inspection warnings' for branch feature/MM-51-update-der-unittests
[18:50:42]W: Cannot find Latest successful build to calculate metric 'number of inspection warnings'
[18:50:42]W: Cannot find Latest successful build, branch: 'feature/MM-51-update-der-unittests' to calculate metric 'number of tests' for branch feature/MM-51-update-der-unittests
[18:50:42]W: Cannot find Latest successful build to calculate metric 'number of tests'
[18:50:42]W: Cannot find Latest successful build, branch: 'feature/MM-51-update-der-unittests' to calculate metric 'number of ignored tests' for branch feature/MM-51-update-der-unittests
[18:50:42]W: Cannot find Latest successful build to calculate metric 'number of ignored tests'
[18:50:43]W: Cannot find Latest successful build, branch: 'feature/MM-51-update-der-unittests' to calculate metric 'artifacts size' for branch feature/MM-51-update-der-unittests
[18:50:43]W: Cannot find Latest successful build to calculate metric 'artifacts size'
Please sign in to leave a comment.
Hi Stefan,
These messages are reported because you have many build failure conditions configured, but there is no build on dedicated branch. Do you see these messages if you run one more build on the same branch?
Regarding slow build, please investigate the case using the guidelines: https://confluence.jetbrains.com/display/TCD10/Common+Problems#CommonProblems-BuildisslowunderTeamCity.
Hello Alina,
thanks for your reply.
As the build always fails (due to Execution timeout) I always see this messages (and it never succeeds). And I only have 9 failure conditions, not 3140 ;-)
The problem is somewhere in the "Visual Studio Tests" build step. The build step starts e.g. at [11:37:24], a little bit later I get the results:
And then I get the about 2000 lines with "Cannot find Latest successful build" and 20 Minutes later (still in this build step) I get the message "[12:02:16][Step 8/11] The build XXXX#2.1.2.0_#21 {buildId=3202} has been running for more than 30 minutes. Terminating..."
I had a quick look at the "Common Problems" but didn't find a solution.
I will open a ticket and send you the build log.
Regards!
Stefan
Is now a bug ticket: https://youtrack.jetbrains.com/issue/TW-48129