[MVE] 1.6.1: TC-ACE-2.4 docker-python and CLI run logging difference

[SamCullen-Element]

Reproduction steps

The log saved by the CLI run does not include the test steps run after commissioning however if run through the python-docker method all evidence is present. The trace-to is default TRUE in the cli and works for other cases just fine.

File size from CLI run: 263kb
File size form Docker run: 22,158kb

Bug prevalence

Whenever run via cli

GitHub hash of the SDK that was being used

df8bd03

Platform

linux

Platform Version(s)

No response

Type

Test Improvement

Testing

CI tested

(Optional) If manually tested please explain why this is only manually tested

No response

Anything else?

No response

[SamCullen-Element]

Also affects ACE-2.1, 2.2, 2.3

[Pradeep-grl]

@rquidute , @antonio-amjr Could you please take a look at this issue.

[SamCullen-Element]

@antonio-amjr this also affects TC-RR-1.1

[SamCullen-Element]

@antonio-amjr something as well. Running a new project the TH hung after the test finished but before it printed out the location of the saved log for a test case it had fully captured before and the log excluded the test steps and only captured the commissioning. Since this event is has not recovered whatever is adding those steps to the log even after a reboot and when run on a completely new project.
Running the python test through the docker still works however in printing all step information.

[antonio-amjr]

@SamCullen-Element @KishokG
What it seems to me is that TH is not prepared for this massive volume of logs from those tests.
Even changing some log handler specifics here, I could see the steps logs and follow the execution but the arrival of all the log entries freezes the CLI's Log Viewer and results in a impressive 80MB of file size (only 1 test case).

I'll investigate this further to see if I can make this better, but all points out as something harder than expected.
Bare with me some a little longer until I investigate in an architecture level.