[
https://issues.apache.org/jira/browse/IGNITE-20468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768765#comment-17768765
]
Pavel Tupitsyn commented on IGNITE-20468:
-----------------------------------------
Hanging tests are caused by IGNITE-17931 (deadlock in
*SchemaRegistryImpl.waitLatestSchema* ). However, we should add timeouts and
avoid waiting forever on some client operations.
> .NET: Thin 3.0: Intermittent timeouts on TC
> -------------------------------------------
>
> Key: IGNITE-20468
> URL: https://issues.apache.org/jira/browse/IGNITE-20468
> Project: Ignite
> Issue Type: Bug
> Components: platforms, thin client
> Affects Versions: 3.0.0-beta1
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Critical
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Increased number of .NET TC builds fail with timeout errors. Investigate
> whether some specific test or behavior is causing this, whether this is a
> problem on server side, etc
> *
> https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunNetTests?branch=%3Cdefault%3E&mode=builds#all-projects
> * `Fail to issue RPC to
> org.apache.ignite.internal.runner.app.PlatformTestNodeRunner_2,
> consecutiveErrorTimes=10, error=Status[ETIMEDOUT<1010>: RPC exception:null]`
> * `OneTimeSetUp: System.TimeoutException : The operation has timed out.`
> ** Which operation? Why is there no stack trace?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
