[jira] [Updated] (IGNITE-8061) GridCachePartitionedDataStructuresFailoverSelfTest.testCountDownLatchConstantMultipleTopologyChange may hang on TeamCity

2020-12-29 Thread Maxim Muzafarov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Muzafarov updated IGNITE-8061:

Fix Version/s: (was: 2.10)

> GridCachePartitionedDataStructuresFailoverSelfTest.testCountDownLatchConstantMultipleTopologyChange
>  may hang on TeamCity
> 
>
> Key: IGNITE-8061
> URL: https://issues.apache.org/jira/browse/IGNITE-8061
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Affects Versions: 2.4
>Reporter: Andrey Kuznetsov
>Priority: Major
> Attachments: log.txt
>
>
> The log attached contains 'Test has been timed out and will be interrupted' 
> message, but does not contain subsequent 'Test has been timed out [test=...'.
> Known facts:
> * There is pending GridDhtColocatedLockFuture in the log.
> * On timeout, InterruptedException comes to doTestCountDownLatch, but 
> finally-block contains the code leading to distributed locking.



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


[jira] [Updated] (IGNITE-8061) GridCachePartitionedDataStructuresFailoverSelfTest.testCountDownLatchConstantMultipleTopologyChange may hang on TeamCity

2020-06-26 Thread Aleksey Plekhanov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Plekhanov updated IGNITE-8061:
--
Fix Version/s: (was: 2.9)
   2.10

> GridCachePartitionedDataStructuresFailoverSelfTest.testCountDownLatchConstantMultipleTopologyChange
>  may hang on TeamCity
> 
>
> Key: IGNITE-8061
> URL: https://issues.apache.org/jira/browse/IGNITE-8061
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Affects Versions: 2.4
>Reporter: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.10
>
> Attachments: log.txt
>
>
> The log attached contains 'Test has been timed out and will be interrupted' 
> message, but does not contain subsequent 'Test has been timed out [test=...'.
> Known facts:
> * There is pending GridDhtColocatedLockFuture in the log.
> * On timeout, InterruptedException comes to doTestCountDownLatch, but 
> finally-block contains the code leading to distributed locking.



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


[jira] [Updated] (IGNITE-8061) GridCachePartitionedDataStructuresFailoverSelfTest.testCountDownLatchConstantMultipleTopologyChange may hang on TeamCity

2019-10-03 Thread Maxim Muzafarov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Muzafarov updated IGNITE-8061:

Fix Version/s: (was: 2.8)
   2.9

> GridCachePartitionedDataStructuresFailoverSelfTest.testCountDownLatchConstantMultipleTopologyChange
>  may hang on TeamCity
> 
>
> Key: IGNITE-8061
> URL: https://issues.apache.org/jira/browse/IGNITE-8061
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Affects Versions: 2.4
>Reporter: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.9
>
> Attachments: log.txt
>
>
> The log attached contains 'Test has been timed out and will be interrupted' 
> message, but does not contain subsequent 'Test has been timed out [test=...'.
> Known facts:
> * There is pending GridDhtColocatedLockFuture in the log.
> * On timeout, InterruptedException comes to doTestCountDownLatch, but 
> finally-block contains the code leading to distributed locking.



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


[jira] [Updated] (IGNITE-8061) GridCachePartitionedDataStructuresFailoverSelfTest.testCountDownLatchConstantMultipleTopologyChange may hang on TeamCity

2018-09-27 Thread Vladimir Ozerov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-8061:

Fix Version/s: (was: 2.7)
   2.8

> GridCachePartitionedDataStructuresFailoverSelfTest.testCountDownLatchConstantMultipleTopologyChange
>  may hang on TeamCity
> 
>
> Key: IGNITE-8061
> URL: https://issues.apache.org/jira/browse/IGNITE-8061
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Affects Versions: 2.4
>Reporter: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
> Attachments: log.txt
>
>
> The log attached contains 'Test has been timed out and will be interrupted' 
> message, but does not contain subsequent 'Test has been timed out [test=...'.
> Known facts:
> * There is pending GridDhtColocatedLockFuture in the log.
> * On timeout, InterruptedException comes to doTestCountDownLatch, but 
> finally-block contains the code leading to distributed locking.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (IGNITE-8061) GridCachePartitionedDataStructuresFailoverSelfTest.testCountDownLatchConstantMultipleTopologyChange may hang on TeamCity

2018-09-25 Thread Nikolay Izhikov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nikolay Izhikov updated IGNITE-8061:

Fix Version/s: (was: 2.8)
   2.7

> GridCachePartitionedDataStructuresFailoverSelfTest.testCountDownLatchConstantMultipleTopologyChange
>  may hang on TeamCity
> 
>
> Key: IGNITE-8061
> URL: https://issues.apache.org/jira/browse/IGNITE-8061
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Affects Versions: 2.4
>Reporter: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.7
>
> Attachments: log.txt
>
>
> The log attached contains 'Test has been timed out and will be interrupted' 
> message, but does not contain subsequent 'Test has been timed out [test=...'.
> Known facts:
> * There is pending GridDhtColocatedLockFuture in the log.
> * On timeout, InterruptedException comes to doTestCountDownLatch, but 
> finally-block contains the code leading to distributed locking.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (IGNITE-8061) GridCachePartitionedDataStructuresFailoverSelfTest.testCountDownLatchConstantMultipleTopologyChange may hang on TeamCity

2018-09-24 Thread Nikolay Izhikov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nikolay Izhikov updated IGNITE-8061:

Fix Version/s: (was: 2.7)
   2.8

> GridCachePartitionedDataStructuresFailoverSelfTest.testCountDownLatchConstantMultipleTopologyChange
>  may hang on TeamCity
> 
>
> Key: IGNITE-8061
> URL: https://issues.apache.org/jira/browse/IGNITE-8061
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Affects Versions: 2.4
>Reporter: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
> Attachments: log.txt
>
>
> The log attached contains 'Test has been timed out and will be interrupted' 
> message, but does not contain subsequent 'Test has been timed out [test=...'.
> Known facts:
> * There is pending GridDhtColocatedLockFuture in the log.
> * On timeout, InterruptedException comes to doTestCountDownLatch, but 
> finally-block contains the code leading to distributed locking.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (IGNITE-8061) GridCachePartitionedDataStructuresFailoverSelfTest.testCountDownLatchConstantMultipleTopologyChange may hang on TeamCity

2018-06-26 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-8061:
---
Fix Version/s: (was: 2.6)
   2.7

> GridCachePartitionedDataStructuresFailoverSelfTest.testCountDownLatchConstantMultipleTopologyChange
>  may hang on TeamCity
> 
>
> Key: IGNITE-8061
> URL: https://issues.apache.org/jira/browse/IGNITE-8061
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Affects Versions: 2.4
>Reporter: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.7
>
> Attachments: log.txt
>
>
> The log attached contains 'Test has been timed out and will be interrupted' 
> message, but does not contain subsequent 'Test has been timed out [test=...'.
> Known facts:
> * There is pending GridDhtColocatedLockFuture in the log.
> * On timeout, InterruptedException comes to doTestCountDownLatch, but 
> finally-block contains the code leading to distributed locking.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (IGNITE-8061) GridCachePartitionedDataStructuresFailoverSelfTest.testCountDownLatchConstantMultipleTopologyChange may hang on TeamCity

2018-04-12 Thread Andrey Kuznetsov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Kuznetsov updated IGNITE-8061:
-
Fix Version/s: (was: 2.5)
   2.6

> GridCachePartitionedDataStructuresFailoverSelfTest.testCountDownLatchConstantMultipleTopologyChange
>  may hang on TeamCity
> 
>
> Key: IGNITE-8061
> URL: https://issues.apache.org/jira/browse/IGNITE-8061
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Affects Versions: 2.4
>Reporter: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.6
>
> Attachments: log.txt
>
>
> The log attached contains 'Test has been timed out and will be interrupted' 
> message, but does not contain subsequent 'Test has been timed out [test=...'.
> Known facts:
> * There is pending GridDhtColocatedLockFuture in the log.
> * On timeout, InterruptedException comes to doTestCountDownLatch, but 
> finally-block contains the code leading to distributed locking.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)