[
https://issues.apache.org/jira/browse/IGNITE-9834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16644824#comment-16644824
]
Ignite TC Bot commented on IGNITE-9834:
---------------------------------------
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Direct IO) 1{color} [[tests 0 JVM CRASH , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2049654]]
{color:#d04437}PDS (Indexing){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2049660]]
* WalRolloverRecordLoggingFsyncTest.testAvoidInfinityWaitingOnRolloverOfSegment
(last started)
{color:#d04437}PDS 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2049658]]
* IgnitePdsTestSuite: BPlusTreePageMemoryImplTest.testMassiveRemove2_false -
0,0% fails in last 100 master runs.
{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=2049702&buildTypeId=IgniteTests24Java8_RunAll]
> ClientImpl shouldn't fail JVM with 130 error code after node validation errors
> ------------------------------------------------------------------------------
>
> Key: IGNITE-9834
> URL: https://issues.apache.org/jira/browse/IGNITE-9834
> Project: Ignite
> Issue Type: Bug
> Reporter: Alexey Platonov
> Assignee: Alexey Platonov
> Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> In the current number of Ignite if client (tcp-client-disco-msg-worker)
> receive validation error message represented by
> TcpDiscoveryCheckFailedMessage then client fail with 130 error code.
> Semantically such behavior is invalid. Client must cancel own work in normal
> order.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
