You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrew Medvedev (JIRA)" <ji...@apache.org> on 2018/05/16 14:02:00 UTC
[jira] [Comment Edited] (IGNITE-5883) Ignite Start Nodes test suite
is flaky
[ https://issues.apache.org/jira/browse/IGNITE-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477461#comment-16477461 ]
Andrew Medvedev edited comment on IGNITE-5883 at 5/16/18 2:01 PM:
------------------------------------------------------------------
There is a pattern:
For successful tests there are logs in artifacts on TC
(run via shell
??Starting remote node with SSH command: nohup "/data/teamcity/work/fe52c920c1589f47/bin/ignite.sh" v "modules/core/src/test/config/spring-start-nodes.xml" -J-DIGNITE_SSH_HOST="127.0.0.1" -J-DIGNITE_SSH_USER_NAME="teamcity" > /data/teamcity/work/fe52c920c1589f47/work/log/ignite-startNodes/05-16-2018-13-13-47-6c1e5bff.log 2>& 1 &??
For every failing tests however the log file is absent. Since this is stderr redirection and the file is just absent I guess the error is very high up stack (may be during this shell command invocation, for example).
In any case given that remote nodes are failing without any error logs I am not sure this problem is traceable at all unless we change something in tests or Teamcity configuration.
was (Author: andmed):
There is a pattern:
For successful tests there are logs in artifacts on TC
(run via shell
Starting remote node with SSH command: nohup "/data/teamcity/work/fe52c920c1589f47/bin/ignite.sh" -v "modules/core/src/test/config/spring-start-nodes.xml" -J-DIGNITE_SSH_HOST="127.0.0.1" -J-DIGNITE_SSH_USER_NAME="teamcity" > /data/teamcity/work/fe52c920c1589f47/work/log/ignite-startNodes/05-16-2018--13-13-47-6c1e5bff.log 2>& 1 &)
For every failing tests however the log file is absent. Since this is stderr redirection and the file is just absent I guess the error is very high up stack (may be during this shell command invocation, for example).
In any case given that remote nodes are failing without any error logs I am not sure this problem is traceable at all unless we change something in tests or Teamcity configuration.
> Ignite Start Nodes test suite is flaky
> --------------------------------------
>
> Key: IGNITE-5883
> URL: https://issues.apache.org/jira/browse/IGNITE-5883
> Project: Ignite
> Issue Type: Bug
> Reporter: Ivan Rakov
> Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> Ignite Start Nodes suite contains several flaky tests.
> Example runs with sporadic fails:
> 1) http://ci.ignite.apache.org/viewLog.html?buildId=746188&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgniteStartNodes
> 2) http://ci.ignite.apache.org/viewLog.html?buildId=747364&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgniteStartNodes
> The ticket is for investigation and making tests stable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)