Hi, Ilya! Thank you for the review!
> For some reason, when I run it locally, it starts to use persistence, do > you have ideas why that would happen? The reason is "Authentication can be enabled only for cluster with enabled persistence." [1] > It also seems to me that > org.apache.ignite.internal.processors.security.compute.closure.ComputeTaskCancelRemoteSecurityContextCheckTest#testClientTaskInitatorCancelOnSrvNode > is flaky. I have started this test 25 times, and it is green. Could you please clarify why do you think the test is flaky? 1. https://github.com/apache/ignite/blob/720706d794e4935779cc2531462595032a547852/modules/core/src/main/java/org/apache/ignite/internal/processors/authentication/IgniteAuthenticationProcessor.java#L158 чт, 7 нояб. 2019 г. в 15:02, Ilya Kasnacheev <ilya.kasnach...@gmail.com>: > Hello! > > I will re-run tests against fresh master, and then commit if they pass. > > For some reason, when I run it locally, it starts to use persistence, do > you have ideas why that would happen? > > It also seems to me that > > org.apache.ignite.internal.processors.security.compute.closure.ComputeTaskCancelRemoteSecurityContextCheckTest#testClientTaskInitatorCancelOnSrvNode > is flaky. > > Regards, > -- > Ilya Kasnacheev > > > чт, 7 нояб. 2019 г. в 12:10, Denis Garus <garus....@gmail.com>: > > > Hello, Igniters! > > > > I've raised the PR [1] for the issue [2]. > > Could somebody review it? > > > > 1. https://github.com/apache/ignite/pull/7017 > > 2. https://issues.apache.org/jira/browse/IGNITE-12300 > > >
