Output message in each project nested to deep hierarchy about xunit-teamcity HOT 3 OPEN

Ah, right. This is caused by the parallel test runs merged in #20. I'm not sure if there is a nice way to avoid this without either buffering the test output (ie, you will not see the output from the test run until the entire assembly has finished), or running in serial instead.
I'll have to have a look at the TeamCity logging API and see if there's an alternative.

from xunit-teamcity.

Hi @aixasz,
It is not fully clear from the screenshot, so just to verify: These are all different, unrelated assemblies being tested, and somehow nested under each other?

from xunit-teamcity.

The problem is in solution contained many test projects, and when xunit teamcity started in build step, it's ran in each project and after finish for a project, it doesn't exit block module of output message, and this will append new block module for next testing project under current project tested.

So after this build step finish the output message show the deep hierarchy.

from xunit-teamcity.