Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
Hi Maxim,
I think it is because the test already failed in master, so bot considers
this test failure in the branch is not an issue.
The bot does not analyze dates and happens-before of builds :). So Run
History for master contains failures, and the bot excludes this test from
blockers.
Dmitry, Dmitry
I've run MTCGA.Bot with additional commenting to JIRA [1] and bot have
shown the report [2] of TC Run all without mentioning
`IgniteOptimizationDateFuncSpec` test failure.
Any ideas why it happens?
[1] https://issues.apache.org/jira/browse/IGNITE-8552
[2]
Vladimir,
Thank you!
On Fri, 21 Sep 2018 at 09:28 Vladimir Ozerov wrote:
> Caused by IGNITE-8552. Will investigate.
>
> пт, 21 сент. 2018 г. в 5:39, :
>
> > Hi Ignite Developer,
> >
> > I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> > I hope you can help.
> >
> >
Caused by IGNITE-8552. Will investigate.
пт, 21 сент. 2018 г. в 5:39, :
> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I hope you can help.
>
> *New test failure in master
>
Igniters,
Tests began constantly fails with an exception - `java.sql.Timestamp cannot
be cast to java.sql.Date`.
The most suspicious commit relates to [1] issue.
I've rerun TC using new MTCGA.Bot feature `comment to the JIRA`.
Test failure can be also found in `pull/4692/head` PR of TC build [2]
Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*New test failure in master
org.apache.ignite.spark.IgniteOptimizationDateFuncSpec.Supported optimized date
functions - FORMATDATETIME
