[
https://issues.apache.org/jira/browse/IGNITE-13619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17220409#comment-17220409
]
Ignite TC Bot commented on IGNITE-13619:
----------------------------------------
{panel:title=Branch: [pull/8390/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Spring (Data){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5690203]]
{panel}
{panel:title=Branch: [pull/8390/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5687360&buildTypeId=IgniteTests24Java8_RunAll]
> Thread dumps on failure processor invocations should be enabled by default
> --------------------------------------------------------------------------
>
> Key: IGNITE-13619
> URL: https://issues.apache.org/jira/browse/IGNITE-13619
> Project: Ignite
> Issue Type: Bug
> Reporter: Mirza Aliev
> Assignee: Mirza Aliev
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Thread dumps on failure processor invocations should be enabled by default.
> It seems this feature was disabled accidentally.
> Also, threadDumpPerFailureTypeTime publication looks as not safe.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
