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: TC Bot triggers Run-All using a random JDK version
Date Wed, 15 May 2019 03:41:14 GMT
JDK 12 both Oracle and Open + JDK 13 Open early access builds.
May be suites require additional configuration — I can do this quick. 


> On 14 May 2019, at 23:43, Dmitriy Pavlov <dpavlov@apache.org> wrote:
> 
> Is Java 12 available on all TeamCity agents?
> 
> вт, 14 мая 2019 г. в 23:21, Petr Ivanov <mr.weider@gmail.com>:
> 
>> How about adding JDK 12 to this list?
>> Or it is a bit prematurely for now?
>> 
>>> On 14 May 2019, at 21:02, Dmitriy Pavlov <dpavlov@apache.org> wrote:
>>> 
>>> Hi Petr,
>>> 
>>> Thank you for your reply. Almost the same term (tag) is used by Bot
>>> internally when the Java version is displayed. So from point of view of
>>> Bot's usability tags are not necessary. From the point of view of main TC
>>> UI - may be.
>>> 
>>> About selection options, it is configured at TC Bot server in the main
>>> Bot's config file - branches.json (section is below). Maybe/someday it
>> will
>>> be configured in the UI or taken from TC settings, but now selection
>>> options are duplicated there.
>>> 
>>> Sincerely,
>>> Dmitriy Pavlov
>>> 
>>> {
>>> "id": "master-nightly",
>>> "chains": [
>>>   {
>>>     "serverId": "apache",
>>>     "suiteId": "IgniteTests24Java8_RunAllNightly",
>>>     "branchForRest": "\u003cdefault\u003e",
>>>     "triggerBuild": true,
>>>     /* Triggering quiet period in minutes. Protects from too-often
>>> triggering in case build is too fast, e.g. compilation failure. */
>>>     "triggerBuildQuietPeriod": 30,
>>>     /** List of build parameters should be specified for triggering
>>> build. Each parameter should have name and may have randomly selected
>>> or fixed value. */
>>>     "triggerParameters": [
>>>       {
>>>         name: "reverse.dep.*.env.JAVA_HOME",
>>>         randomValue: true,
>>>         "selection": [
>>>           {value:"%env.JDK_ORA_18%", label:"JDK8"},
>>>           {value:"%env.JDK_ORA_9%", label:"JDK9"},
>>>           {value:"%env.JDK_ORA_10%", label:"JDK10"},
>>>           {value:"%env.JDK_OPEN_11%", label:"JDK11"}
>>>         ]
>>>       }
>>>     ]
>>>   }
>>> ]
>>> 
>>> }
>>> 
>>> чт, 9 мая 2019 г. в 20:12, Petr Ivanov <mr.weider@gmail.com>:
>>> 
>>>> I can make builds autotag itself with used JDK.
>>>> 
>>>> Also - from what JDKs does randomiser choose?
>>>> 
>>>>> On 9 May 2019, at 12:56, Dmitriy Pavlov <dpavlov@apache.org> wrote:
>>>>> 
>>>>> Hi Igniters,
>>>>> 
>>>>> For your information, Apache Ignite TeamCity bot now triggers run all
>>>>> (nightly) using some available JDK version (random each time). Used JDK
>>>> is
>>>>> saved in the Bot DB and is shown at UI (see below).
>>>>> 
>>>>> Next step could be changing the flakyness detection algorithm in the
>> Bot
>>>> to
>>>>> analyze run history using only a particular Java version.
>>>>> 
>>>>> Sincerely,
>>>>> Dmitriy Pavlov
>>>>> 
>>>>> PDS (Compatibility) [ tests 5 ] JDK8
>>>>> ⚂ IgniteCompatibilityBasicTestSuite:
>>>>> 
>>>> 
>> PersistenceBasicCompatibilityTest.testNodeStartByOldVersionPersistenceData_2_2
>>>>> (fail
>>>>> rate 28,2%)
>>>>> ⚂ 🐞 IgniteCompatibilityBasicTestSuite:
>>>>> FoldersReuseCompatibilityTest.testFoldersReuseCompatibility_2_2 (fail
>>>> rate
>>>>> 22,7%)
>>>>> 
>>>>> Cache (Restarts) 1 [ tests 0 TIMEOUT , Exit Code ] JDK11  1 running
>>>> Critical
>>>>> F.R.: 12,5%
>>>>>   Thread Dump
>>>> 
>>>> 
>> 
>> 


Mime
View raw message