You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/04/20 13:11:25 UTC
[jira] [Commented] (IGNITE-3019) Implement config variations test
for IgniteCompute
[ https://issues.apache.org/jira/browse/IGNITE-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249653#comment-15249653 ]
ASF GitHub Bot commented on IGNITE-3019:
----------------------------------------
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/658
IGNITE-3019 Implement config variations test for IgniteCompute
IGNITE-3019 Implement config variations test for IgniteCompute
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-3019
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/658.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 #658
----
commit 3e0fdceb3c8512689e34dc101b687e3e537c686c
Author: tledkov-gridgain <tl...@gridgain.com>
Date: 2016-04-19T15:42:24Z
IGNITE-3019 Implement config variations test for IgniteCompute
commit 3e6274da0b2ad517763792d009d2cb132788708c
Author: tledkov-gridgain <tl...@gridgain.com>
Date: 2016-04-20T10:50:00Z
IGNITE-3019 add tests for call and affinityCall
commit 3fb06ae0722ad288fe608a19e6943f1175c83987
Author: tledkov-gridgain <tl...@gridgain.com>
Date: 2016-04-20T10:53:04Z
Merge branch 'master' of https://github.com/gridgain/apache-ignite into ignite-3019
----
> Implement config variations test for IgniteCompute
> --------------------------------------------------
>
> Key: IGNITE-3019
> URL: https://issues.apache.org/jira/browse/IGNITE-3019
> Project: Ignite
> Issue Type: Test
> Components: compute
> Reporter: Semen Boikov
> Assignee: Taras Ledkov
> Fix For: 1.6
>
>
> Need implement configuration variations test for IgniteCompute (see IgniteCacheBasicConfigVariationsFullApiTestSuite as example).
> Test should cover following cases:
> - all supported marshaller (Optimized, Binary, JDK)
> - different data types for task parameters/return values (see IgniteConfigVariationsAbstractTest.runInAllDataModes)
> - single server node
> - multiple servers, multiple clients, use IgniteCompue API from servers and clients
> - true/false for IgniteConfiguration.peerClassLoadingEnabled
> - true/false for IgniteConfiguration.marshalLocalJobs
> - need test following types of jobs classes: regular class, Serializable, Externalizable, Binarylizable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)