New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TeamCity logger uses wrong flowid #2385
Comments
This is a very common complaint I'm hearing in all the teams I work with. |
Me Also, one repo has 60+ test projects so it's pretty chatty 😿 |
TeamCity can potentially suppress TeamCity messages from XUnit by excluding the TEAMCITY_PROJECT_NAME environment variable from spawned processes. I am thinking of doing this for the .NET runner. |
@NikolayPianikov tbh, I wouldn't because there's a risk it would break tests. |
I have a potential fix that does the following:
Here are some results from me running a single test class:
(I restructured the tests slightly to ensure that we had passing, failing, and skipped tests, as well as ensuring that at least one test had output, so we could see all the output messages.) |
This will be shipped in the next 2.5.0 prerelease build (whatever comes after build 11). If any TeamCity users can test this to ensure that it's working as expected that'd be wonderful. 😄 |
Several people reported in my project that their "test collection" messages are shown outside the intended block. I can confirm but it never got too important to me. However, with a large amount of tests, I guess it can be bothering to scroll between build summary and individual targets:
After talking with @NikolayPianikov it appears that the
flowId
inTeamCityReporterMessageHandler
is the reason. To my knowledge it is random. A better way would be to set it from the environment variableTEAMCITY_PROCESS_FLOW_ID
. Nikolay may correct me on this.The text was updated successfully, but these errors were encountered: