[
https://issues.jboss.org/browse/ISPN-2508?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2508:
----------------------------------------
That assertion is not right. You're comparing threadRunningExecutor, which gets
assigned to the main thread since it's executed outside the listener executor, and
that's indeed equals to the main thread that executes the assertion. Not really sure
what you're trying to assert there, but I guess what you wanna be comparing is that
the thread that the executor thread creates is the same one used to run the async
listener.
The async executor is executed synchronously
---------------------------------------------
Key: ISPN-2508
URL:
https://issues.jboss.org/browse/ISPN-2508
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Reporter: Anna Manukyan
Assignee: Galder Zamarreño
Labels: testsuite_stability
The functional tests which are testing the custom asynchronous executor, are failing with
JDG-6.1.0.ER1 build due to the following reason:
the tests are verifying that the executor was executed in separate thread, i.e.
asynchronously, but starting from the new Infinispan version, the executor's execution
thread is the same as the one where the test is executed.
You can find the failing test results here:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-jdbc-cache-sto...
and here:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-jdbc-cache-sto...
The test is located here:
https://svn.devel.redhat.com/repos/jboss-qa/jdg/jdg-functional-tests/trun...
Best regards,
Anna.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira