[
https://issues.jboss.org/browse/ISPN-2508?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2508:
----------------------------------------
Once again, the test failures are not there :(
Hmmmm, we already have a test that verifies that the async notification thread is
different to the application thread:
https://github.com/infinispan/infinispan/blob/master/core/src/test/java/o...
The test is passing, so maybe there's something else we need to look into? Can't
see the failures to get an idea of the assert that's now failing.
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
Fix For: 5.2.0.CR1
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