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

Ignite TC Bot commented on IGNITE-11059:
----------------------------------------

{panel:title=--> Run :: All: Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}SPI (URI Deploy){color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=3199607]]
* IgniteUriDeploymentTestSuite: 
GridHttpDeploymentSelfTest.testDeployUndeploy2Files - 0,0% fails in last 76 
master runs.
* IgniteUriDeploymentTestSuite: GridHttpDeploymentSelfTest.testSameContantFiles 
- 0,0% fails in last 76 master runs.

{color:#d04437}MVCC Queries{color} [[tests 
5|https://ci.ignite.apache.org/viewLog.html?buildId=3199609]]
* IgniteCacheMvccSqlTestSuite: 
CacheMvccPartitionedSqlCoordinatorFailoverTest.testSqlReadInsideTxInProgressCoordinatorFails_ReadDelay
 - 0,0% fails in last 273 master runs.
* IgniteCacheMvccSqlTestSuite: 
CacheMvccPartitionedSqlCoordinatorFailoverTest.testAccountsTxSql_SingleNode_CoordinatorFails_Persistence
 - 0,0% fails in last 0 master runs.
* IgniteCacheMvccSqlTestSuite: 
CacheMvccReplicatedSqlCoordinatorFailoverTest.testAccountsTxSql_SingleNode_CoordinatorFails_Persistence
 - 0,0% fails in last 0 master runs.

{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3195514&buildTypeId=IgniteTests24Java8_RunAll]

> Print information about pending locks queue in case of dht local tx timeout.
> ----------------------------------------------------------------------------
>
>                 Key: IGNITE-11059
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11059
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexei Scherbakov
>            Assignee: Ivan Daschinskiy
>            Priority: Major
>              Labels: newbie
>             Fix For: 2.8
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Currently in case of dht local tx timeout it's hard to understand which keys 
> was not locked.
> Addtional information should be printed in log on timeout containing 
> information about pending keys:
> key, tx info holding a lock (xid, label if present)



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

Reply via email to