This may be related to the recent changes in TC infrastructure. I see the following in remote nodes output:
nohup: ignoring input /data/teamcity/work/820be461cd64b574/bin/ignite.sh, ERROR: The version of JAVA installed in JAVA_HOME= is incorrect. Please point JAVA_HOME variable to installation of JDK 1.7 or JDK 1.8. You can also download latest JDK at http://java.com/download Sergey, Petr, can you take a look? 2017-12-15 15:23 GMT+03:00 Petr Ivanov <mr.wei...@gmail.com>: > According to Failure Conditions [1] — it is designed to fail after 30 min. > So the question is - should we consider 30 min run time to be project’s > error (and fix the code) or TeamCity error (and fix the build configuration > by, for example, increasing build failure timeout)? > > > [1] https://ci.ignite.apache.org/admin/editBuildFailureConditions. > html?id=buildType:Ignite20Tests_IgniteStartNodes < > https://ci.ignite.apache.org/admin/editBuildFailureConditions. > html?id=buildType:Ignite20Tests_IgniteStartNodes> > > > > On 15 Dec 2017, at 14:50, Dmitry Pavlov <dpavlov....@gmail.com> wrote: > > > > Hi Igniters, > > > > Who can became Jedi of TeamCity and substitute me in this research? > > > > Sincerely, > > Dmitry Pavlov > > > > пт, 15 дек. 2017 г. в 12:38, Anton Vinogradov <avinogra...@gridgain.com > >: > > > >> Dmitry, > >> > >> Could you please investigate? > >> > >> On Fri, Dec 15, 2017 at 9:16 AM, Andrey Kuznetsov <stku...@gmail.com> > >> wrote: > >> > >>> Hi Anton, > >>> > >>> I doubt it was merge conflict. Couple of days ago 'Ignite Start Nodes' > >>> suite succeeded 1 time after unrelated changes, and now it is failing > >>> again. > >>> > >>> 2017-12-12 16:25 GMT+03:00 Anton Vinogradov <avinogra...@gridgain.com > >: > >>> > >>>> Hi, > >>>> > >>>> Seems we have merge conflict. > >>>> > >>>> https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_ > >>>> IgniteStartNodes&tab=buildTypeHistoryList&branch_ > >>>> Ignite20Tests=%3Cdefault%3E > >>>> > >>>> > >>>> -- > >>> Best regards, > >>> Andrey Kuznetsov. > >>> > >> > >