ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitry Pavlov <dpavlov....@gmail.com>
Subject Re: New test failures in .NET
Date Fri, 16 Mar 2018 13:09:56 GMT
I did this TC verification before merge. Have no idea why I missed it.

пт, 16 мар. 2018 г. в 16:06, Pavel Tupitsyn <ptupitsyn@apache.org>:

> Hi,
>
> The problem is introduced by our freshman committer Nikolay Izhikov in
> "IGNITE-7756: IgniteUuid added to predefined types" [1]
>
> IgniteUuid type id has changed on Java side, but not in .NET.
> I have pushed the fix to master branch.
>
> I can only ask everyone again to have some respect for your fellow Igniters
> and verify changes on TeamCity before merging. It is not that hard.
>
> Thank you,
> Pavel
>
>
>
> [1] https://github.com/apache/ignite/commit/70ca86a30a7589f9ff46
> 6b93a958362135347d02
>
>
>
> On Fri, Mar 16, 2018 at 2:51 PM, Dmitry Pavlov <dpavlov.spb@gmail.com>
> wrote:
>
> > Hi,
> >
> > There are 31 test failures in .NET tests https://ci.ignite.apache.org/
> > viewLog.html?buildId=1137460&tab=buildResultsDiv&buildTypeId=
> > IgniteTests24Java8_IgnitePlatformNet
> >  Unfortunately it continues to reproduce.
> >
> > Igniters, who can advice how to fix it? Was there any changes in .NET
> > tests/new tests contributions?
> >
> > It seems there is one issue here, because 1st failure
> > "SetUp method failed. SetUp : System.NullReferenceException : Object
> > reference not set to an instance of an object."
> > and consequent failures are about Ignite instances.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message