You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (JIRA)" <ji...@apache.org> on 2019/07/08 11:46:00 UTC
[jira] [Commented] (IGNITE-11952) Bug fixes and improvements in
console utilities & test fixes
[ https://issues.apache.org/jira/browse/IGNITE-11952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16880245#comment-16880245 ]
Ignite TC Bot commented on IGNITE-11952:
----------------------------------------
{panel:title=--> Run :: All: Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET{color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=4270359]]
* exe: IgniteConfigurationTest.TestSpringXml
{color:#d04437}Platform .NET (Core Linux){color} [[tests 5|https://ci.ignite.apache.org/viewLog.html?buildId=4290052]]
* dll: IgnitionStartTest.TestIgniteStartsFromSpringXml
{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=4263318&buildTypeId=IgniteTests24Java8_RunAll]
> Bug fixes and improvements in console utilities & test fixes
> ------------------------------------------------------------
>
> Key: IGNITE-11952
> URL: https://issues.apache.org/jira/browse/IGNITE-11952
> Project: Ignite
> Issue Type: Bug
> Reporter: Sergey Chugunov
> Assignee: Sergey Chugunov
> Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Contains the following fixes:
> * U.currentTimeMillis() must not be used for timeouts calculation in Discovery and Communication SPI
> * control.sh --baseline shows incorrect information
> * control.sh print unclear message (secured cluster)
> * Client disconnect detection time linearly depends on number of network interfaces of remote node
> * Various improvements in javadocs
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)