What determines when build problems get reported as "new" on the build summary page

We're noticing that if 2 builds in a row print the same service message (either as error or as a buildProblem), the problem gets reported as new both times


What causes this behaviour and how can we stop it from happening? (Expected behaviour is that the first time it happens it gets reported as new and if it occurs in the next run it doesn't report as a new problem)



Hi Adam,

You are right. TC shouldn't report the same problem twice as a new problem. This is in the same build configuration, right? Could you please provide a screenshot (feel free to mask any sensitive content)? What TC version do you use?

I'll try reproducing the problem, so having the exact service message you use to report the build problem may help. Could you please provide it?

Hi Mikhail,


This is within the same build configuration

We're on TeamCity Professional 2022.10.1 (build 116934)


Here's a screenshot showing relevant snippets from two builds (I made a shelf with an intentional error in this so I could get a reliable repro, I can sift through our builds to find this happening organically if that's preferable)


We print error messages by going

print(f"##teamcity[message text='{formatted_message}' errorDetails='' status='ERROR']", flush=True)


We print build problem messages by going

print(f"##teamcity[buildProblem description='{message}']", flush=True)

with my understanding being that by not providing an identity argument we're just using the message as a fallback


In this example, the build problem is

D:\BuildAgent\work\12f79e4c46ead2d2\Engine\Source\Runtime\CoreUObject\Private\UObject\UObjectHash.cpp(13): fatal error C1083: Cannot open include file: 'HAL/FakeFile.h': No such file or directory

but it isn't specific to one service message 

Hi Adam,

I reproduced the issue. It only appears when a new problem is reported for the first time in a personal build. TC will continue reporting the same problem as 'new' in personal builds until it appears in a regular build. In this regular build, the problem will also be marked as new, and from this point forward, TC will acknowledge the problem as a known one.

Personal builds are special in this regard because other users who don't see your personal builds may face the same problem in their own personal builds, and they would want it to be marked as 'new'.

I'm checking with the team on whether it's a bug. I'll update you as soon as I have anything.
Hi Adam,

Apolgies for the delay. I submitted a new bug report: https://youtrack.jetbrains.com/issue/TW-79729/The-same-problem-reported-as-new-in-consequent-personal-builds. Feel free to vote for the it, leave comments, and subscribe to the updates. See this article if you are still getting familiar with YouTrack: https://intellij-support.jetbrains.com/hc/articles/207241135.

Sounds good, thank you Mikhail!


Please sign in to leave a comment.