[GitHub] ignite pull request: Ignite 1692 Test Suite and extended logging f...

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request: Ignite 1692 Test Suite and extended logging f...

andrey-kuznetsov
GitHub user ilantukh opened a pull request:

    https://github.com/apache/ignite/pull/289

    Ignite 1692 Test Suite and extended logging for DataStreamProcessorSelfTest.

   

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ilantukh/ignite ignite-1692

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/289.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #289
   
----
commit 0ae52562db085e795b441a61a135ee30dd1815fb
Author: Ilya Lantukh <[hidden email]>
Date:   2015-12-02T12:02:25Z

    Test Suite for DataStreamProcessorSelfTest.testReplicated.

commit 749323ea246105505ed3d1ded077592c6def59c1
Author: Ilya Lantukh <[hidden email]>
Date:   2015-12-03T09:43:15Z

    Extended logging for DataStreamProcessorSelfTest.testReplicated.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request: Ignite 1692 Test Suite and extended logging f...

andrey-kuznetsov
Github user ilantukh closed the pull request at:

    https://github.com/apache/ignite/pull/289


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---