[jira] [Commented] (IGNITE-12316) Extend test coverage [IGNITE-10761] GridCacheProcessor should add info about cache in exception message, if applicable.

2019-10-28 Thread Vyacheslav Koptilin (Jira) 


[ 
https://issues.apache.org/jira/browse/IGNITE-12316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16961017#comment-16961017
 ] 

Vyacheslav Koptilin commented on IGNITE-12316:
--

Hello [~ktkale...@gridgain.com],

The tests look good to me!

> Extend test coverage [IGNITE-10761] GridCacheProcessor should add info about 
> cache in exception message, if applicable.
> ---
>
> Key: IGNITE-12316
> URL: https://issues.apache.org/jira/browse/IGNITE-12316
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Test cache operations that should fail inside tx thread
> ||*Forbidden operation inside transaction*||
> |dynamic single cache start|
> |dynamic start of multiple caches|
> |dynamic cache destroy|
> |dynamic destroy of multiple caches|
> |dynamic cache close|
> |reset cache state|
> {quote}org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicSingleCacheStart
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicStartMultipleCaches
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicCacheDestroy
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicDestroyMultipleCaches
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicCacheClose
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testResetCacheState\{quote}
> # Start cluster, start active transaction in thread
> # Assert that in *Forbidden operation inside transaction* scenarios exception 
> occurs with log information about cache name and reason
> # Finish running transaction, assert that there is no exception while 
> evaluating *Forbidden operation inside transaction*
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-12316) Extend test coverage [IGNITE-10761] GridCacheProcessor should add info about cache in exception message, if applicable.

2019-10-25 Thread Kirill Tkalenko (Jira) 


[ 
https://issues.apache.org/jira/browse/IGNITE-12316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16959810#comment-16959810
 ] 

Kirill Tkalenko commented on IGNITE-12316:
--

[~ivan.glukos] Please merge.

> Extend test coverage [IGNITE-10761] GridCacheProcessor should add info about 
> cache in exception message, if applicable.
> ---
>
> Key: IGNITE-12316
> URL: https://issues.apache.org/jira/browse/IGNITE-12316
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Test cache operations that should fail inside tx thread
> ||*Forbidden operation inside transaction*||
> |dynamic single cache start|
> |dynamic start of multiple caches|
> |dynamic cache destroy|
> |dynamic destroy of multiple caches|
> |dynamic cache close|
> |reset cache state|
> {quote}org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicSingleCacheStart
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicStartMultipleCaches
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicCacheDestroy
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicDestroyMultipleCaches
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicCacheClose
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testResetCacheState\{quote}
> # Start cluster, start active transaction in thread
> # Assert that in *Forbidden operation inside transaction* scenarios exception 
> occurs with log information about cache name and reason
> # Finish running transaction, assert that there is no exception while 
> evaluating *Forbidden operation inside transaction*
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-12316) Extend test coverage [IGNITE-10761] GridCacheProcessor should add info about cache in exception message, if applicable.

2019-10-23 Thread Kirill Tkalenko (Jira) 


[ 
https://issues.apache.org/jira/browse/IGNITE-12316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16957850#comment-16957850
 ] 

Kirill Tkalenko commented on IGNITE-12316:
--

[~slava.koptilin] Please make code review.

> Extend test coverage [IGNITE-10761] GridCacheProcessor should add info about 
> cache in exception message, if applicable.
> ---
>
> Key: IGNITE-12316
> URL: https://issues.apache.org/jira/browse/IGNITE-12316
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Test cache operations that should fail inside tx thread
> ||*Forbidden operation inside transaction*||
> |dynamic single cache start|
> |dynamic start of multiple caches|
> |dynamic cache destroy|
> |dynamic destroy of multiple caches|
> |dynamic cache close|
> |reset cache state|
> {quote}org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicSingleCacheStart
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicStartMultipleCaches
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicCacheDestroy
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicDestroyMultipleCaches
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicCacheClose
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testResetCacheState\{quote}
> # Start cluster, start active transaction in thread
> # Assert that in *Forbidden operation inside transaction* scenarios exception 
> occurs with log information about cache name and reason
> # Finish running transaction, assert that there is no exception while 
> evaluating *Forbidden operation inside transaction*
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-12316) Extend test coverage [IGNITE-10761] GridCacheProcessor should add info about cache in exception message, if applicable.

2019-10-23 Thread Sergey Antonov (Jira) 


[ 
https://issues.apache.org/jira/browse/IGNITE-12316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16957835#comment-16957835
 ] 

Sergey Antonov commented on IGNITE-12316:
-

[~ktkale...@gridgain.com] I'm okay with your changes.

> Extend test coverage [IGNITE-10761] GridCacheProcessor should add info about 
> cache in exception message, if applicable.
> ---
>
> Key: IGNITE-12316
> URL: https://issues.apache.org/jira/browse/IGNITE-12316
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Test cache operations that should fail inside tx thread
> ||*Forbidden operation inside transaction*||
> |dynamic single cache start|
> |dynamic start of multiple caches|
> |dynamic cache destroy|
> |dynamic destroy of multiple caches|
> |dynamic cache close|
> |reset cache state|
> {quote}org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicSingleCacheStart
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicStartMultipleCaches
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicCacheDestroy
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicDestroyMultipleCaches
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicCacheClose
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testResetCacheState\{quote}
> # Start cluster, start active transaction in thread
> # Assert that in *Forbidden operation inside transaction* scenarios exception 
> occurs with log information about cache name and reason
> # Finish running transaction, assert that there is no exception while 
> evaluating *Forbidden operation inside transaction*
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-12316) Extend test coverage [IGNITE-10761] GridCacheProcessor should add info about cache in exception message, if applicable.

2019-10-23 Thread Ignite TC Bot (Jira) 


[ 
https://issues.apache.org/jira/browse/IGNITE-12316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16957715#comment-16957715
 ] 

Ignite TC Bot commented on IGNITE-12316:


{panel:title=Branch: [pull/6995/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4716307buildTypeId=IgniteTests24Java8_RunAll]

> Extend test coverage [IGNITE-10761] GridCacheProcessor should add info about 
> cache in exception message, if applicable.
> ---
>
> Key: IGNITE-12316
> URL: https://issues.apache.org/jira/browse/IGNITE-12316
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Test cache operations that should fail inside tx thread
> ||*Forbidden operation inside transaction*||
> |dynamic single cache start|
> |dynamic start of multiple caches|
> |dynamic cache destroy|
> |dynamic destroy of multiple caches|
> |dynamic cache close|
> |reset cache state|
> {quote}org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicSingleCacheStart
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicStartMultipleCaches
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicCacheDestroy
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicDestroyMultipleCaches
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testDynamicCacheClose
> org.apache.ignite.internal.processors.cache.GridCacheProcessorActiveTxTest#testResetCacheState\{quote}
> # Start cluster, start active transaction in thread
> # Assert that in *Forbidden operation inside transaction* scenarios exception 
> occurs with log information about cache name and reason
> # Finish running transaction, assert that there is no exception while 
> evaluating *Forbidden operation inside transaction*
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)