testMultipleExecuteWithInitialResults was not actually testing anything because it fired off asynchronous tasks, but failed to see if those tasks threw an exception.
Before this fix, the test always got an exception. It installed a test hook to prevent the CQ from starting. That prevented any events from being queued up. The test then waited for all events to be received on the client, which timed out. Reimplemented the test to test the condition described in the comments, making sure that calling executeWithInitialResults twice does not lose events that are queued up already. Thank you for submitting a contribution to Apache Geode. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [ ] Has your PR been rebased against the latest commit within the target branch (typically `develop`)? - [ ] Is your initial contribution a single, squashed commit? - [ ] Does `gradlew build` run cleanly? - [ ] Have you written or updated unit tests to verify your changes? - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? ### Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. If you need help, please send an email to [email protected]. [ Full content available at: https://github.com/apache/geode/pull/2682 ] This message was relayed via gitbox.apache.org for [email protected]
