[
https://issues.jboss.org/browse/ISPN-2508?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on ISPN-2508:
-----------------------------------------------
Anna Manukyan <amanukya(a)redhat.com> made a comment on [bug
869174|https://bugzilla.redhat.com/show_bug.cgi?id=869174]
Hi Galder,
thanks a lot for hint.
The interesting thing is that, this assertion was passing successfully during JDG
6.0.1.CR1 testing, but after adding some logs, I've got what was wrong.
The test is fixed.
Best regards,
Anna.
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