Roman Puchkovskiy created IGNITE-18618:
------------------------------------------
Summary: Test timeout is too short in Dotnet tests
Key: IGNITE-18618
URL: https://issues.apache.org/jira/browse/IGNITE-18618
Project: Ignite
Issue Type: Bug
Components: platforms
Reporter: Roman Puchkovskiy
Attachments: _Test_Run_.NET_Tests_7879.log.zip
In a log from
[https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunNetTests/7024431?hideProblemsFromDependencies=false&hideTestsFromDependencies=false&pluginCoverage=true&expandBuildTestsSection=true]
(attached to this ticket) the following can be seen:
[12:06:40] : [dotnet test] Passed TestReplaceExact [65 ms]
[12:06:42] : [dotnet test] Jan 24, 2023 11:06:42 AM
io.scalecube.cluster.membership.MembershipProtocolImpl
lambda$onDeadMemberDetected$42
[12:06:42] : [dotnet test] INFO:
[default:org.apache.ignite.internal.runner.app.PlatformTestNodeRunner_2:[email protected]:3345]
Member leaved without notification:
default:org.apache.ignite.internal.runner.app.PlatformTestNodeRunner:[email protected]:3344...
skipped ...[12:06:43] : [dotnet test] INFO: Node added to the logical
topology [node=org.apache.ignite.internal.runner.app.PlatformTestNodeRunner]
[12:06:46] : [dotnet test] [11:06:46] [Info] [ClientFailoverSocket] Primary
socket connection lost, reconnecting.... skipped ...[12:06:46] : [dotnet test]
Failed TestContains [6 s]
[12:06:46] : [dotnet test] Error Message:
[12:06:46] : [dotnet test] System.TimeoutException : The operation has
timed out.
Looks like a node left and returned back (a probable reason for leaving is a GC
pause), but it took a few seconds because it's guided by timeouts. So it seems
that the timeout of 5 seconds is too low in Dotnet tests, it should be probably
set to a higher value.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
