;
> >--- Forwarded message ---
> >From: "Ivan Pavlukhin" < vololo...@gmail.com >
> >To: dev < dev@ignite.apache.org >
> >Cc:
> >Subject: Re: Cache 6 suite is broken
> >Date: Fri, 20 Dec 2019 10:04:07 +0300
> >
> >FYI
Looks like i found problem root cause, first run completed on TC, hope it would
be ok with other builds.
>
>
>--- Forwarded message ---
>From: "Ivan Pavlukhin" < vololo...@gmail.com >
>To: dev < dev@ignite.apache.org >
>Cc:
>Subject: Re: Cach
FYI
I applied the patch.
ср, 18 дек. 2019 г. в 14:46, Ivan Pavlukhin :
>
> So, if nobody objects, I will merge PR [1] on Friday.
>
> [1] https://github.com/apache/ignite/pull/7142
>
> ср, 18 дек. 2019 г. в 13:13, Dmitriy Pavlov :
> >
> > Hi Ivan, Igniters,
> >
> > My proposal is to apply PR and t
So, if nobody objects, I will merge PR [1] on Friday.
[1] https://github.com/apache/ignite/pull/7142
ср, 18 дек. 2019 г. в 13:13, Dmitriy Pavlov :
>
> Hi Ivan, Igniters,
>
> My proposal is to apply PR and take a look to wider statistics in the
> master branch. WDYT?
>
> Sincerely,
> Dmitriy Pavlo
Hi Ivan, Igniters,
My proposal is to apply PR and take a look to wider statistics in the
master branch. WDYT?
Sincerely,
Dmitriy Pavlov
ср, 18 дек. 2019 г. в 09:36, Ivan Pavlukhin :
> Igniters,
>
> I run tests several times for my PR [1] and results [2] looks somehow
> better than in master [3]
Igniters,
I run tests several times for my PR [1] and results [2] looks somehow
better than in master [3]. But the problematic test seems too flaky.
So, I cannot decide between 2 options:
1. Apply PR [1].
2. Ignore the problematic test.
(Unfortunately do not have a chance to investigate and fix)
An update. After increasing NetworkTimeout [1] the test passes rarely [2].
[1] https://github.com/apache/ignite/pull/7142/files
[2]
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache6?branch=pull%2F7142%2Fhead&buildTypeTab=overview
пн, 16 дек. 2019 г. в 09:07, Ivan Pavlukhi
Hi,
I noticied that Cache 6 suite finishes badly (exit code 137) almost
everytime [1] on master. It started recently. A problematic test
inside is IgniteCache150ClientsTest. I made some attempts to fix the
test (including reverting recent commits), but had no luck. And a hard
part here is that I d
