No test logs if TestNG Test has timeout parameter about client-java HOT 6 CLOSED

As a possible solution we can use InheritedThreadLocal for every Thread, except main. This will probably work for TestNG and JUnit5, since the first one is using main thread only for Suite creation and the second one is not using main thread at all. But what if some frameworks use main thread in the same way as other threads?

from client-java.

I think this relates to #91

I suggested a (apparently naive) Pull Request at the time, but it was reverted after additional issues appeared:
#53

Perhaps someone can pick this up and find a better solution

from client-java.

Yes, that's client issue due to ThreadLocal we use in our logging contexts. I believe we need to redesign it, but not in current (v5) version.

from client-java.

@HardNorth is there any progress on this? Perhaps this can be parameterized in the client and defaulted to the existing behavior? and frameworks that need this behavior can update to use this setting to solve this issue.

from client-java.

@dagansandler not yet, the issue has milestone 6 since it requires serious logging logic rewrite. Currently I'm working on milestone 5.1, which is related to Android compatibility.

from client-java.

Fixed in #183

from client-java.