You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 29, 2022. It is now read-only.
TestNG creating separate threads for all test items if timeout is set. Then we have situation while runningNowItemId field in ReportPortalListenerContext.java is being set from test item thread, and read from main thread on a log message creation. As runningNowItemId is a ThreadLocal object we will get null value in main thread.
The text was updated successfully, but these errors were encountered:
Dependencies:
agent-java-testng:2.6.0
logger-java-log4j:2.6.0
logger-java-logback:2.6.0
org.testng:testng:6.9.8
org.apache.logging.log4j:log4j-core:2.4
Bug description:
User use testNG as a test runner. If test item have a timeout, log is not being sent to RP.
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd" >
<suite name="Menu" verbose="1" time-out="1">
Looks like this issue is related to a testng-team/testng#914
TestNG creating separate threads for all test items if timeout is set. Then we have situation while runningNowItemId field in ReportPortalListenerContext.java is being set from test item thread, and read from main thread on a log message creation. As runningNowItemId is a ThreadLocal object we will get null value in main thread.
The text was updated successfully, but these errors were encountered: