[
https://issues.jboss.org/browse/ISPN-4784?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-4784:
------------------------------------
The tests should start with a call to {{TestResourceTracker.backgroundTestStarted()}},
which sets the test name in the thread local. I guess the "Test name not set"
log message should also mention this...
Note that TestResourceTracker doesn't really need the thread name to contain the test
name, but it would be nice to do it anyway so that log filtering works in the TRACE CI
build.
TestResourceTracker not working properly for OSGi tests
--------------------------------------------------------
Key: ISPN-4784
URL:
https://issues.jboss.org/browse/ISPN-4784
Project: Infinispan
Issue Type: Enhancement
Components: Test Suite - Core
Affects Versions: 7.0.0.Beta2
Reporter: Ion Savin
Assignee: Dan Berindei
The OSGi tests are running in a different process from the test driver and are executed
through RMI. The assumptions that the test name is contained in the thread name and that
there's a one-to-one mapping from thread to test is no longer valid (ThreadLocal used
for the test name).
Executing the tests in integrationtests/osgi will result in many log messages similar to
this one:
{noformat}
Test name not set in unknown thread RMI TCP Connection(3)-127.0.0.1
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)