No test logs if TestNG Test has timeout parameter

[VolodymyrLykhachov]

I faced with no logs in RP when I specify timeout parameter in TestNG Test annotation. All events that are relayed to start/stop/methods reflected fine in RP, but no logging from TestNG test that I send through RP appender.
Here is example of @Test annotation
@Test(description = "test", dataProvider = "DataProvider", alwaysRun = true, timeout = 60)

in DEBUG MODE
event.getmessage() has correct message, but
in com.epam.reportportal.service.ReportPortal.emitLog next variable is null

LoggingContext loggingContext = LoggingContext.CONTEXT_THREAD_LOCAL.get();
loggingContext = null

after removing timeout parameter all work well

[dagansandler]

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

[HardNorth]

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.

[HardNorth]

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?

[dagansandler]

@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.

[HardNorth]

@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.

[HardNorth]

Fixed in #183