IgniteSpiTestSuite is called from ’SPI’ build type and I’ve added agent filter there. IgniteKernalSelfTestSuite is not found in build types.
> On 27 Jun 2018, at 11:26, Nikolay Izhikov <nizhi...@apache.org> wrote: > > Well, it's a good question :) > > I've added encryption tests in `IgniteKernalSelfTestSuite` and in > `IgniteSpiTestSuite`. > Not sure, what builds on Team City runs these suites. > > В Ср, 27/06/2018 в 11:18 +0300, Petr Ivanov пишет: >> Nikolay, >> >> >> What is “core” module? >> >> >>> On 27 Jun 2018, at 00:42, Nikolay Izhikov <nizhi...@apache.org> wrote: >>> >>> Hello, Petr. >>> >>> Thanks a lot! >>> I see success spring encryption tests now [1] >>> >>> I've added encryption tests to core module also. >>> Can we set same rule for a core module? >>> >>> [1] >>> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-2290193573767653560&tab=testDetails >>> >>> >>> В Вт, 26/06/2018 в 23:38 +0300, Petr Ivanov пишет: >>>> I’ve added JCE as it is described in documentation, but for some unknown >>>> reason it won’t work on 1.8.0_u151. >>>> So I’ve fix agent filter rule to run Spring build type only on 1.8.0_u171 >>>> (49 agents) and run it on all enabled compatible agents. >>>> Looks like it fixed the issue. >>>> >>>> >>>> >>>>> On 26 Jun 2018, at 19:27, Nikolay Izhikov <nizhi...@apache.org> wrote: >>>>> >>>>> Petr, can you make suggested jdk upgrade? >>>>> >>>>> В Пн, 25/06/2018 в 14:28 +0300, Nikolay Izhikov пишет: >>>>>> Petr. >>>>>> >>>>>> One more thing: >>>>>> >>>>>> We need to install "Java Cryptography Extension (JCE) Unlimited Strength >>>>>> Jurisdiction Policy Files" [1] to enable usage of JDK provided crypto >>>>>> algorithmes. >>>>>> Otherwise it fails with "java.security.InvalidKeyException: Illegal key >>>>>> size at javax.crypto.Cipher.checkCryptoPerm(Cipher.java:1039)" [2] >>>>>> >>>>>> Can you do it for Team City agents? >>>>>> >>>>>> [1] >>>>>> http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html >>>>>> [2] >>>>>> https://ci.ignite.apache.org/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=1421337&_focus=30899 >>>>>> >>>>>> В Пн, 25/06/2018 в 13:24 +0300, Petr Ivanov пишет: >>>>>>> I’ve modified filter requirements for JDK for Spring build >>>>>>> configuration to run only on u151/u171 of JDK-1.8.0 (it will be 55 >>>>>>> agent). >>>>>>> Hope this will be enough. >>>>>>> >>>>>>> >>>>>>> >>>>>>>> On 25 Jun 2018, at 12:54, Nikolay Izhikov <nizhi...@apache.org> wrote: >>>>>>>> >>>>>>>> Hello, Petr. >>>>>>>> >>>>>>>>> I can temporarily assign special rule for agent JDK and fix theirs >>>>>>>>> Java later. >>>>>>>> >>>>>>>> I'm not Team City guru, so I'm don't understand your proposal :) >>>>>>>> >>>>>>>> All I need is make sure Core and Spring suites for my branch [1] are >>>>>>>> executed with latest jdk. >>>>>>>> >>>>>>>> Can you make it for me? >>>>>>>> >>>>>>>> [1] https://github.com/apache/ignite/pull/4167 >>>>>>>> >>>>>>>> >>>>>>>> В Пн, 25/06/2018 в 11:21 +0300, Petr Ivanov пишет: >>>>>>>>> Nokolay, >>>>>>>>> >>>>>>>>> >>>>>>>>> Agents prior publicagent10 has u77 inded, while publicagent10-17 has >>>>>>>>> already u171. >>>>>>>>> I can temporarily assign special rule for agent JDK and fix theirs >>>>>>>>> Java later. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> On 25 Jun 2018, at 10:33, Nikolay Izhikov <nizhi...@apache.org> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> Hello, Igniters. >>>>>>>>>> >>>>>>>>>> I'm trying to run tests for TDE branch. >>>>>>>>>> >>>>>>>>>> It seems I'm facing with known JDK bug [1] >>>>>>>>>> Here is log from Team City [2]. >>>>>>>>>> >>>>>>>>>> As I can see current Team City jdk is 1.8.0_77-b03 >>>>>>>>>> Issue JDK-8149411 fixed in 8u102. >>>>>>>>>> >>>>>>>>>> Can we upgrade JDK on Team City? >>>>>>>>>> >>>>>>>>>> [1] https://bugs.openjdk.java.net/browse/JDK-8149411 >>>>>>>>>> [2] >>>>>>>>>> https://ci.ignite.apache.org/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=1420504&_focus=28867 >>
