[
https://issues.apache.org/jira/browse/IGNITE-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16627017#comment-16627017
]
Ivan Fedotov commented on IGNITE-8619:
--------------------------------------
[~dpavlov] I rerun tests.
It remains only one "possible blocker" [.NET
inspections|https://mtcga.gridgain.com/pr.html?serverId=apache&suiteId=IgniteTests24Java8_RunAll&baseBranchForTc=&branchForTc=pull%2F4314%2Fhead&action=Latest],
I tried to rerun it several times, but when I looked in the history of this
test, it becomes clear that
[master|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformNetInspections&tab=buildTypeHistoryList&branch_IgniteTests24Java8=%3Cdefault%3E]
also has such problem in the recent 6 runs.
So I think that now there are no possible blockers according this ticket.
> Remote node could not start in ssh connection
> ---------------------------------------------
>
> Key: IGNITE-8619
> URL: https://issues.apache.org/jira/browse/IGNITE-8619
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Ivan Fedotov
> Assignee: Ivan Fedotov
> Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Now there is a problem with launch remote node via ssh. Initially was an
> assumption that it's due to remote process has not enough time to write
> information into log:
> [IGNITE-8085|https://issues.apache.org/jira/browse/IGNITE-8085]. But this
> correction didn't fix [TeamCity
> |https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=6814497542781613621&tab=testDetails]
> (IgniteProjectionStartStopRestartSelfTest.testStartFiveNodesInTwoCalls).
> So it's necessary to make launch remote node via ssh always succesful.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
