Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <CALUCNEsGU4CfkR4SKe1R+sNg6-MYCk-FPvJgd8X3OjKDo3L=wg@mail.gmail.com>
References: <CALUCNEutcd53ALhLF5iJoZwyfwh_4=gc37yU3yViPGYA4feGDg@mail.gmail.com>
 <CABDss3iWF6UDteYSDouKKck8nyFm7mHr+Jcu5VkRm7Di1LxPzA@mail.gmail.com>
 <CALUCNEtnWaCGyKdjck5PnxN9NydEU1xayuLf6K6JUouSL_=v5Q@mail.gmail.com>
 <CABDss3iEYjtBTEMT8XeN4DtkoUQtXXi6SyiFisJoiPugoumC+A@mail.gmail.com>
 <CALUCNEs6NcNBi0FO=z=aW3dxQt0x_AyXffSHMDd7GBcj-5QxRw@mail.gmail.com>
 <CAFx+i-aUYzuNX70kDstg4xcXxScaORhNOT64nW6Z-kWSjg15+A@mail.gmail.com> <CALUCNEsGU4CfkR4SKe1R+sNg6-MYCk-FPvJgd8X3OjKDo3L=wg@mail.gmail.com>
From: Semyon Boikov <sboikov@gridgain.com>
Date: Fri, 26 May 2017 14:48:56 +0300
Message-ID: <CAFx+i-bUVxMHHmwaqR=nQnJYGYps3sfS0=vBY20Z-=kCQLXgBg@mail.gmail.com>
Subject: Re: Ignite 2.0 TeamCity Run configurations
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary="001a1138e49c25c61a05506bec9e"
archived-at: Fri, 26 May 2017 11:49:02 -0000

--001a1138e49c25c61a05506bec9e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

What about 'Ignite H2 Indexing' suite', it does not execute any test?

On Fri, May 26, 2017 at 2:18 PM, Dmitry Pavlov <dpavlov.spb@gmail.com>
wrote:

> Hi Semen,
>
>
>
> Thank you for this fix. It is correct to replace to IgniteCacheTestSuite4
> in new 2.0 run configurations as we don=E2=80=99t have Binary* analogue.
>
>
>
> IgniteBinaryBasicTestSuite was not deleted to avoid failures in old run
> configurations. I assumed missing test suite will cause failure on
> teamcity. But the first issue shows us it is not a problem. I=E2=80=99ll =
prepare PR
> for removing suite.
>
>
>
> IgniteBinaryObjectsCacheTestSuite3 is kept together with
> IgniteCacheTestSuite3 for backward compatibility. In Ignite 2.0 tests fir=
st
> is used, and in Ignite tests - second. And if someone runs old run config=
s
> then most test will be executed anyway. Practice shows not everyone in
> community uses new Run Configs for master-based PRs. In future we will be
> able to remove not necessary suite.
>
>
> Sincerely,
>
> Dmitriy Pavlov
>
>
>
> =D0=BF=D1=82, 26 =D0=BC=D0=B0=D1=8F 2017 =D0=B3. =D0=B2 14:00, Semyon Boi=
kov <sboikov@gridgain.com>:
>
> > I just found that 'Ignite Cache 4' was not executed on TeamCity since i=
t
> > 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 delete=
d?
> >
> > Thanks
> >
> > On Mon, May 22, 2017 at 6:39 PM, Dmitry Pavlov <dpavlov.spb@gmail.com>
> > wrote:
> >
> > > Igniters,
> > >
> > > I've created new PR https://github.com/apache/ignite/pull/1986 withou=
t
> > > merge conflicts against master. Please review these changes instead o=
f
> > > PR1956.
> > >
> > > Thank you
> > >
> > > Best Regards,
> > > Dmitry Pavlov
> > >
> > > =D0=BF=D0=BD, 22 =D0=BC=D0=B0=D1=8F 2017 =D0=B3. =D0=B2 13:21, Alexey=
 Goncharuk <
> alexey.goncharuk@gmail.com
> > >:
> > >
> > > > Thanks, Dmitriy!
> > > >
> > > > If there are no other objections, I will merge the changes shortly.
> > > >
> > > > 2017-05-22 13:10 GMT+03:00 Dmitry Pavlov <dpavlov.spb@gmail.com>:
> > > >
> > > > > 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
> > > > >
> > > > > =D1=81=D1=80, 17 =D0=BC=D0=B0=D1=8F 2017 =D0=B3. =D0=B2 20:52, Al=
exey Goncharuk <
> > > alexey.goncharuk@gmail.com
> > > > >:
> > > > >
> > > > > > Great news! Looking forward to getting rid of the unnecessary T=
C
> > > > > > configurations.
> > > > > >
> > > > > > Once this is done, I think we should also work out if we can us=
e
> > > 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 <dpavlov.spb@gmail.com
> >:
> > > > > >
> > > > > > > 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 us at least 12
> > machine-hours
> > > > for
> > > > > > each
> > > > > > > test run and in future will allow us to get test results
> faster.
> > > > > > >
> > > > > > > Do you have concerns or remarks about using new run
> > configurations
> > > > for
> > > > > > all
> > > > > > > 2.0+ pull requests?
> > > > > > >
> > > > > > > We are now doing final checks of compatibility of these run
> > > > > > configurations
> > > > > > > with code. Any ideas about what is to be migrated are
> > appreciated.
> > > > > > >
> > > > > > > Best Regards,
> > > > > > > Dmitry Pavlov
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

--001a1138e49c25c61a05506bec9e--