[
https://issues.apache.org/jira/browse/IGNITE-13441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399683#comment-17399683
]
Maxim Muzafarov commented on IGNITE-13441:
------------------------------------------
[~ascherbakov]
Personally, I'd prefer the 'one commit per fixing problem' strategy. The
investigation of bulk commits a really difficult.
As for the current issue - the fix is in the master branch however it seems
that the root cause still not fix. This is confusing.
https://github.com/apache/ignite/commit/f45c470e12c6187afca16996d9c01ddb9fa79869
I see two options here:
- revert this commit and rework it
- change the issue description (what exactly was fixed) than close this issue
and open another one with left problems
> Cache (Restarts) 1 failed with Execution timeout
> ------------------------------------------------
>
> Key: IGNITE-13441
> URL: https://issues.apache.org/jira/browse/IGNITE-13441
> Project: Ignite
> Issue Type: Task
> Reporter: Nikita Tolstunov
> Assignee: Alexey Scherbakov
> Priority: Major
> Attachments:
> Ignite_Tests_2.4_Java_8_9_10_11_Cache_Restarts_1_22724.log.zip
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Suite [Cache(Restarts)
> 1|https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CacheRestarts1?branch=%3Cdefault%3E&mode=builds]
> regularly fails with execution timeout.
> I found that in some cases
> IgniteCacheNearRestartRollbackSelfTest#testRestarts caused it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
