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
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.igni
Hi Igniters,
Who can became Jedi of TeamCity and substitute me in this research?
Sincerely,
Dmitry Pavlov
пт, 15 дек. 2017 г. в 12:38, Anton Vinogradov :
> Dmitry,
>
> Could you please investigate?
>
> On Fri, Dec 15, 2017 at 9:16 AM, Andrey Kuznetsov
> wrote:
>
> > Hi Anton,
> >
> > I doubt i
Dmitry,
Could you please investigate?
On Fri, Dec 15, 2017 at 9:16 AM, Andrey Kuznetsov 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 A
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 :
> Hi,
>
> Seems we have merge conflict.
>
> https://ci.ignite.apache.org/viewType.html?build
Hi,
Seems we have merge conflict.
https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgniteStartNodes&tab=buildTypeHistoryList&branch_Ignite20Tests=%3Cdefault%3E
On Tue, Dec 12, 2017 at 3:55 PM, Andrey Kuznetsov wrote:
> Hi Igniters,
>
> IgniteProjectionStartStopRestartSelfTe
Hi Igniters,
IgniteProjectionStartStopRestartSelfTest fails with timeout on TeamCity,
maybe due to some infrastructure issues. Can anybody take a look?
--
Best regards,
Andrey Kuznetsov.