Can you pinpoint exact string in log where another Ignite node is interfering,
please?
> On 10 Feb 2021, at 11:50, Mikhail Petrov wrote:
>
> Here is an example - [1].
>
> [1] -
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteExtensions_Tests_SpringTransactions&branch_IgniteExt
Here is an example - [1].
[1] -
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteExtensions_Tests_SpringTransactions&branch_IgniteExtensions_Tests=%3Cdefault%3E&tab=buildTypeStatusDiv
On 10.02.2021 11:39, Petr Ivanov wrote:
Very good, thanks!
I will prepare build shortly.
About
Very good, thanks!
I will prepare build shortly.
About flakiness — send me link to build where problem is, I will try to
investigate.
> On 10 Feb 2021, at 11:17, Mikhail Petrov wrote:
>
> Petr, ticket [1] was merged to the master branch. TC build is ok now - [2].
> Sometimes i faced that some
Petr, ticket [1] was merged to the master branch. TC build is ok now -
[2]. Sometimes i faced that some tests can be flaky because test nodes
were trying to join extra incompatible node that does not belong to the
test. But I think we could investigate it in a separate ticket.
Could I ask you
I've updated Extensions template to use only Linux agents.
Will wait for ticket in master, thanks!
> On 10 Feb 2021, at 01:05, Mikhail Petrov wrote:
>
> Hi, Petr.
>
> It seems that the problem is in an outdated version of the maven surefire
> plugin that is used in ignite-extensions.
>
> I
Hi, Petr.
It seems that the problem is in an outdated version of the maven
surefire plugin that is used in ignite-extensions.
I created the corresponding ticket [1].
I also faced that current ignite-extensions build is broken on windows
agents - [2]. It fails with the following error:
/[22
Hi, Nikolay.
I've created a set of tests for extensions, and part of them are failing with:
JUnit4Provider.invoke:159->executeTestSet:238->executeWithRerun:273->execute:365
» NoSuchMethod
java.lang.NoSuchMethodError:
org.apache.maven.surefire.report.SimpleReportEntry.withException(Ljava/lang/S