Failure Reasons break upon upgrading to Teamcity 10.0

[koerbcm]

We had our build results outputting elapsed time and reason for failures, which always gives us "Process exited with code 1", and Fail Tests to our slack channel. We upgraded on Monday morning, and since I brought everything back up, the elapsed time and reason persist, however, the failed tests no longer show. The config hasn't changed and still states it should be sending them.

[PeteGoo]

Hmmmm. Haven't had a chance to test against TC 10 yet

[koerbcm]

Had a feeling. Just wanted to throw this your way. :-)

[103683]

It's a bug, not question. Failure reasons don't show in teamcity 10.

[koerbcm]

I'm not a java guy, but I have looked around. No idea what the issue could be, but seeing as thou the failure reason seems to always be, Failed tests detected, Process exited with code 1 some context around that within Slack again would be pretty great and make this tool a lot more powerful. Appreciate what you guys do. Thanks.

[koerbcm]

Any thoughts on what could have happened to cause this?

[marvin-w]

Can someone please provide some information on what the expected result should be?
(Screenshots would also be great)

[koerbcm]

Here you go @pointerxr. Is this what you were looking for? Does this help? Thank you so much for reviewing this for us.

Before Teamcity 10 (Failed Tests show):

After Teamcity 10 (Failed tests no longer show):

[koerbcm]

Guess there is proprietary info in the screenshots. gonna edit them and post again.

[marvin-w]

You dont need to, I got it ;)

thanks anyway 💃

[marvin-w]

I'm gonna take a deeper look today in the evening/ weekend when I have more time to debug and stuff.

[stephanos]

ah, we just ran into the exact same issue.
is this difficult to fix?

[koerbcm]

@stephanos I haven't found a fix or workaround yet but I don't know Java very well so I haven't been able to really dig in.

[pjohnkeane]

Hey - anyone know if this is specifically impacting TC10, or if it's TC10 and later?