Re: Ignite 2.0 TeamCity Run configurations

Igniters, I've found one more suite without tests: "Ignite Cache Failover Multi JVM" (org.apache.ignite.testsuites.IgniteCacheFailoverMJTestSuite). Currently has paused triggers, but anyway started from Ignite 2.0 snapshot dependecies. Is it required? Alex (al.psc) do you know? it is required in

Re: Ignite 2.0 TeamCity Run configurations

Thank you! I've commited removal of both suites to PR https://github.com/apache/ignite/pull/2014 пт, 26 мая 2017 г. в 14:53, Vladimir Ozerov : > No, we should remote this suite. > > On Fri, May 26, 2017 at 2:48 PM, Semyon Boikov > wrote: > > > What

Re: Ignite 2.0 TeamCity Run configurations

No, we should remote this suite. On Fri, May 26, 2017 at 2:48 PM, Semyon Boikov wrote: > What about 'Ignite H2 Indexing' suite', it does not execute any test? > > On Fri, May 26, 2017 at 2:18 PM, Dmitry Pavlov > wrote: > > > Hi Semen, > > > > > > >

Re: Ignite 2.0 TeamCity Run configurations

What about 'Ignite H2 Indexing' suite', it does not execute any test? On Fri, May 26, 2017 at 2:18 PM, Dmitry Pavlov wrote: > Hi Semen, > > > > Thank you for this fix. It is correct to replace to IgniteCacheTestSuite4 > in new 2.0 run configurations as we don’t have

Re: Ignite 2.0 TeamCity Run configurations

I just found that 'Ignite Cache 4' was not executed on TeamCity since it has from suite name in configuration, I fixed it to use IgniteCacheTestSuite4, is it correct? Aslo why we need both IgniteBinaryObjectsCacheTestSuite3 and IgniteCacheTestSuite3? And why IgniteBinaryBasicTestSuite is not

Re: Ignite 2.0 TeamCity Run configurations

Igniters, I've created new PR https://github.com/apache/ignite/pull/1986 without merge conflicts against master. Please review these changes instead of PR1956. Thank you Best Regards, Dmitry Pavlov пн, 22 мая 2017 г. в 13:21, Alexey Goncharuk : > Thanks, Dmitriy! >

Re: Ignite 2.0 TeamCity Run configurations

Thanks, Dmitriy! If there are no other objections, I will merge the changes shortly. 2017-05-22 13:10 GMT+03:00 Dmitry Pavlov : > Hi, Igniters! > > Could you please review and merge changes from > https://github.com/apache/ignite/pull/1956 into master. > > These changes

Re: Ignite 2.0 TeamCity Run configurations

Hi, Igniters! Could you please review and merge changes from https://github.com/apache/ignite/pull/1956 into master. These changes makes running tests with similar results in TC Run configs "Ignite 2.0 Tests" as it is in "Ignite Tests". Best regards, Dmitry Pavlov ср, 17 мая 2017 г. в 20:52,

Re: Ignite 2.0 TeamCity Run configurations

Great news! Looking forward to getting rid of the unnecessary TC configurations. Once this is done, I think we should also work out if we can use build once, run tests approach for RunAll configuration. Does anybody have a clue if this is possible? 2017-05-17 20:46 GMT+03:00 Dmitry Pavlov

Ignite 2.0 TeamCity Run configurations

Hi, Igniters! Alex (al.psc) has created new Teamcity run configurations optimized for running 2.0 version and later. This project and its run configurations avoid duplicate tests running for binary and default marshallers because it is now the same for 2.0+. Usage of this run configuration saves