ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Petr Ivanov <mr.wei...@gmail.com>
Subject Re: TDE: Upgrade Team City JDK
Date Fri, 10 Aug 2018 09:11:07 GMT
Nikolay, thanks for helping with tests.


I will proceed with Java updates. Will notify when finished.




> On 10 Aug 2018, at 11:37, Nikolay Izhikov <nizhikov@apache.org> wrote:
> 
> Hello, Petr.
> 
> TDE tests succeed on "publicagent03_9091".
> 
> https://ci.ignite.apache.org/viewLog.html?buildId=1626049&buildTypeId=IgniteTests24Java8_BasicTestsWithPersistence&tab=testsInfo
> 
>> If everything is OK — I’ll distribute this Java among all other agents.
> 
> Can you do it?
> 
> В Чт, 09/08/2018 в 18:29 +0300, Petr Ivanov пишет:
>> Done
>> 
>> 
>>> On 9 Aug 2018, at 17:44, Nikolay Izhikov <nizhikov@apache.org> wrote:
>>> 
>>> Petr.
>>> 
>>> Seems, now I has to put my tests in "Basic Tests With Persistence".
>>> Can you configure Team city so I can run "Basic Tests With Persistence" on publicagent03_9091?
>>> 
>>> В Чт, 09/08/2018 в 16:35 +0300, Petr Ivanov пишет:
>>>> Yeap.
>>>> 
>>>> As it is disabled, it will not take tasks from queue automatically, but can
be assigned tasks manually.
>>>> 
>>>> 
>>>>> On 9 Aug 2018, at 16:27, Nikolay Izhikov <nizhikov@apache.org>
wrote:
>>>>> 
>>>>> Hello, Petr.
>>>>> 
>>>>> I'm able to select thi agent for build.
>>>>> But it has "disabled" comment.
>>>>> 
>>>>> Is that OK?
>>>>> 
>>>>> https://ci.ignite.apache.org/viewQueued.html?itemId=1620053:0:153&tab=queuedBuildOverviewTab
>>>>> 
>>>>> В Ср, 08/08/2018 в 17:44 +0300, Petr Ivanov пишет:
>>>>>> Nikolay,
>>>>>> 
>>>>>> 
>>>>>> I’ve updated publicagent03_9091 and tested all current builds for
Ignite Tests 2.4+ project for master branch.
>>>>>> Please test your PR on this agent (select it when starting build)
for correct java configuration.
>>>>>> 
>>>>>> If everything is OK — I’ll distribute this Java among all other
agents.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>> On 31 Jul 2018, at 22:18, Petr Ivanov <mr.weider@gmail.com>
wrote:
>>>>>>> 
>>>>>>>> 8u111.
>>>>>>> 
>>>>>>> I’ve started the process of update, will try to accomplish
by the end of the week.
>>>>>>> 
>>>>>>> 
>>>>>>>> On 31 Jul 2018, at 21:26, Denis Magda <dmagda@apache.org>
wrote:
>>>>>>>> 
>>>>>>>> Nikolay,
>>>>>>>> 
>>>>>>>> Do you need 8u111 and later? Or any JDK 8 works for you?
>>>>>>>> 
>>>>>>>> --
>>>>>>>> Denis
>>>>>>>> 
>>>>>>>> On Tue, Jul 31, 2018 at 6:55 AM Nikolay Izhikov <nizhikov@apache.org>
wrote:
>>>>>>>> 
>>>>>>>>> Hello, Petr.
>>>>>>>>> 
>>>>>>>>>> What JDK is required for running this build?
>>>>>>>>> 
>>>>>>>>> 8u111 and later.
>>>>>>>>> 
>>>>>>>>>> I can filter agents with correct JDK for now.
>>>>>>>>> 
>>>>>>>>> Encryption tests are executed by following build plans:
>>>>>>>>> 
>>>>>>>>>    * Basic 1
>>>>>>>>>    * Binary Objects (Simple Mapper Basic)
>>>>>>>>>    * Queries 1
>>>>>>>>>    * Spring
>>>>>>>>> 
>>>>>>>>> В Вт, 31/07/2018 в 16:45 +0300, Petr Ivanov пишет:
>>>>>>>>>> No we cannot do it right now.
>>>>>>>>>> 
>>>>>>>>>> What JDK is required for running this build?
>>>>>>>>>> I can filter agents with correct JDK for now.
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>>> On 31 Jul 2018, at 16:35, Nikolay Izhikov <nizhikov@apache.org>
wrote:
>>>>>>>>>>> 
>>>>>>>>>>> Hello, Igniters.
>>>>>>>>>>> 
>>>>>>>>>>> I have to up this thread.
>>>>>>>>>>> 
>>>>>>>>>>> TDE. Phase 1 development is over.
>>>>>>>>>>> But, I still can't run TDE tests on Team city
[1].
>>>>>>>>>>> 
>>>>>>>>>>> I think that source of error is [2]
>>>>>>>>>>> 
>>>>>>>>>>> Can we upgrade Team City JDK?
>>>>>>>>>>> 
>>>>>>>>>>> [1]
>>>>>>>>> 
>>>>>>>>> https://ci.ignite.apache.org/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=1566703&_focus=446976
>>>>>>>>>>> [2] https://bugs.openjdk.java.net/browse/JDK-8149411
>>>>>>>>>>> 
>>>>>>>>>>> В Ср, 27/06/2018 в 18:50 +0300, Nikolay Izhikov
пишет:
>>>>>>>>>>>> Hi.
>>>>>>>>>>>> 
>>>>>>>>>>>>> can we add option enables AES 128
>>>>>>>>>>>> 
>>>>>>>>>>>> Currently, 128 bit key used [1]
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>>> I guess we should update environment
to meet test requirements
>>>>>>>>> 
>>>>>>>>> prior putting changes to master.
>>>>>>>>>>>> 
>>>>>>>>>>>> Yes.
>>>>>>>>>>>> 
>>>>>>>>>>>> [1]
>>>>>>>>> 
>>>>>>>>> https://github.com/apache/ignite/pull/4167/files#diff-1088ffe504f1aa300830e1ae9c030de1R80
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> В Ср, 27/06/2018 в 18:44 +0300, Dmitry
Pavlov пишет:
>>>>>>>>>>>>> Hi Nikolay,
>>>>>>>>>>>>> 
>>>>>>>>>>>>> can we add option enables AES 128 for
test mode? This should work
>>>>>>>>> 
>>>>>>>>> well
>>>>>>>>>>>>> without update env.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Sincerely,
>>>>>>>>>>>>> 
>>>>>>>>>>>>> ср, 27 июн. 2018 г. в 18:43, Petr
Ivanov <mr.weider@gmail.com>:
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> On 27 Jun 2018, at 18:06, Nikolay
Izhikov <nizhikov@apache.org>
>>>>>>>>> 
>>>>>>>>> wrote:
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Hello, Eduard.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> We should make suites which
are restricted by agents to make
>>>>>>>>> 
>>>>>>>>> as small
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> as> possible.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Agree. That means we should enable
java cryptography on all
>>>>>>>>> 
>>>>>>>>> agents.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Isn't it?
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> So, I strictly against adding
such test (therefore
>>>>>>>>> 
>>>>>>>>> restriction) to
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> these> suites.>
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> What is wrong with tests?
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Tests in current configuration require
specific environment.
>>>>>>>>>>>>>> I guess we should update environment
to meet test requirements
>>>>>>>>> 
>>>>>>>>> prior
>>>>>>>>>>>>>> putting changes to master.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Do you looked at it or something?
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> В Ср, 27/06/2018 в 14:24
+0300, Eduard Shangareev пишет:
>>>>>>>>>>>>>>>> Nikolay, Petr,
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> We should make suites which
are restricted by agents to make
>>>>>>>>> 
>>>>>>>>> as small as
>>>>>>>>>>>>>>>> possible.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> So, I strictly against adding
such test (therefore
>>>>>>>>> 
>>>>>>>>> restriction) to these
>>>>>>>>>>>>>>>> suites.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> On Wed, Jun 27, 2018 at 11:39
AM, Petr Ivanov <
>>>>>>>>> 
>>>>>>>>> mr.weider@gmail.com>
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> 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 <
>>>>>>>>> 
>>>>>>>>> nizhikov@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 <
>>>>>>>>> 
>>>>>>>>> nizhikov@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 <
>>>>>>>>> 
>>>>>>>>> nizhikov@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 <
>>>>>>>>> 
>>>>>>>>> nizhikov@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 <
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> nizhikov@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
>>>>>>>>>> 
>>>>>>>>>> 
>> 


Mime
View raw message