TC patch validation

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

TC patch validation

Konstantin Boudnik-2
Gents,

is TC still picking up the JIRAs in PA state? Somehow it seems that only the
latest changes from master are being picked.

On a somewhat similar note: can I run tests for just a single module? E.g. in
IGNITE-1701 I made some changes in ignite-spark pom.xml and want to quickly
verify that this doesn't affect anything (which it shouldn't, clearly).
Running the whole testset on my tiny laptop will probably take a few hours.

Appreciate any pointers, thanks in advance!
  Cos


signature.asc (237 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: TC patch validation

Ivan V.
Hi, Konstantin,
Tests are grouped in suites by subsystems. You can run particular test
suite -- e.g. "Ignite Hadoop".
To run the tests with particular changes push the "Run..." button near that
test suite and chose "pull/<your-pull-request-number>/head" in "Build
branch" field on the "Changes" tab.

On Fri, Oct 16, 2015 at 1:01 AM, Konstantin Boudnik <[hidden email]> wrote:

> Gents,
>
> is TC still picking up the JIRAs in PA state? Somehow it seems that only
> the
> latest changes from master are being picked.
>
> On a somewhat similar note: can I run tests for just a single module? E.g.
> in
> IGNITE-1701 I made some changes in ignite-spark pom.xml and want to quickly
> verify that this doesn't affect anything (which it shouldn't, clearly).
> Running the whole testset on my tiny laptop will probably take a few hours.
>
> Appreciate any pointers, thanks in advance!
>   Cos
>
>
Reply | Threaded
Open this post in threaded view
|

Re: TC patch validation

dsetrakyan
I think Cos’ question also was why the patches attached to Jira do not get
automatically run on TC. To my knowledge, the automatic runs were disabled,
but I am not sure if it includes patches as well.

Can someone clarify how to run patches on TC?

D.

On Fri, Oct 16, 2015 at 2:16 AM, Ivan Veselovskiy <[hidden email]
> wrote:

> Hi, Konstantin,
> Tests are grouped in suites by subsystems. You can run particular test
> suite -- e.g. "Ignite Hadoop".
> To run the tests with particular changes push the "Run..." button near that
> test suite and chose "pull/<your-pull-request-number>/head" in "Build
> branch" field on the "Changes" tab.
>
> On Fri, Oct 16, 2015 at 1:01 AM, Konstantin Boudnik <[hidden email]>
> wrote:
>
> > Gents,
> >
> > is TC still picking up the JIRAs in PA state? Somehow it seems that only
> > the
> > latest changes from master are being picked.
> >
> > On a somewhat similar note: can I run tests for just a single module?
> E.g.
> > in
> > IGNITE-1701 I made some changes in ignite-spark pom.xml and want to
> quickly
> > verify that this doesn't affect anything (which it shouldn't, clearly).
> > Running the whole testset on my tiny laptop will probably take a few
> hours.
> >
> > Appreciate any pointers, thanks in advance!
> >   Cos
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: TC patch validation

Artem Shutak
Yes, automatic runs were disabled for patches too.

To run patches you can use "Run All for patch" with specified jira number
at "Paramethers / Jira number*".

-- Artem --

On Thu, Oct 22, 2015 at 4:11 AM, Dmitriy Setrakyan <[hidden email]>
wrote:

> I think Cos’ question also was why the patches attached to Jira do not get
> automatically run on TC. To my knowledge, the automatic runs were disabled,
> but I am not sure if it includes patches as well.
>
> Can someone clarify how to run patches on TC?
>
> D.
>
> On Fri, Oct 16, 2015 at 2:16 AM, Ivan Veselovskiy <
> [hidden email]
> > wrote:
>
> > Hi, Konstantin,
> > Tests are grouped in suites by subsystems. You can run particular test
> > suite -- e.g. "Ignite Hadoop".
> > To run the tests with particular changes push the "Run..." button near
> that
> > test suite and chose "pull/<your-pull-request-number>/head" in "Build
> > branch" field on the "Changes" tab.
> >
> > On Fri, Oct 16, 2015 at 1:01 AM, Konstantin Boudnik <[hidden email]>
> > wrote:
> >
> > > Gents,
> > >
> > > is TC still picking up the JIRAs in PA state? Somehow it seems that
> only
> > > the
> > > latest changes from master are being picked.
> > >
> > > On a somewhat similar note: can I run tests for just a single module?
> > E.g.
> > > in
> > > IGNITE-1701 I made some changes in ignite-spark pom.xml and want to
> > quickly
> > > verify that this doesn't affect anything (which it shouldn't, clearly).
> > > Running the whole testset on my tiny laptop will probably take a few
> > hours.
> > >
> > > Appreciate any pointers, thanks in advance!
> > >   Cos
> > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: TC patch validation

Konstantin Boudnik-2
On Thu, Oct 22, 2015 at 01:28PM, Artem Shutak wrote:
> Yes, automatic runs were disabled for patches too.
>
> To run patches you can use "Run All for patch" with specified jira number
> at "Paramethers / Jira number*".

Right, that presumes that a user has an account. I am sure I have one, but I
lost the password, because of the changes of the laptop and whatnot. There's
no obvious name to reset it though; Artem could you help me to reset it and
drop me a password separately or via skype?

Thank you very much in advance!
  Cos

>
> -- Artem --
>
> On Thu, Oct 22, 2015 at 4:11 AM, Dmitriy Setrakyan <[hidden email]>
> wrote:
>
> > I think Cos’ question also was why the patches attached to Jira do not get
> > automatically run on TC. To my knowledge, the automatic runs were disabled,
> > but I am not sure if it includes patches as well.
> >
> > Can someone clarify how to run patches on TC?
> >
> > D.
> >
> > On Fri, Oct 16, 2015 at 2:16 AM, Ivan Veselovskiy <
> > [hidden email]
> > > wrote:
> >
> > > Hi, Konstantin,
> > > Tests are grouped in suites by subsystems. You can run particular test
> > > suite -- e.g. "Ignite Hadoop".
> > > To run the tests with particular changes push the "Run..." button near
> > that
> > > test suite and chose "pull/<your-pull-request-number>/head" in "Build
> > > branch" field on the "Changes" tab.
> > >
> > > On Fri, Oct 16, 2015 at 1:01 AM, Konstantin Boudnik <[hidden email]>
> > > wrote:
> > >
> > > > Gents,
> > > >
> > > > is TC still picking up the JIRAs in PA state? Somehow it seems that
> > only
> > > > the
> > > > latest changes from master are being picked.
> > > >
> > > > On a somewhat similar note: can I run tests for just a single module?
> > > E.g.
> > > > in
> > > > IGNITE-1701 I made some changes in ignite-spark pom.xml and want to
> > > quickly
> > > > verify that this doesn't affect anything (which it shouldn't, clearly).
> > > > Running the whole testset on my tiny laptop will probably take a few
> > > hours.
> > > >
> > > > Appreciate any pointers, thanks in advance!
> > > >   Cos
> > > >
> > > >
> > >
> >

signature.asc (237 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: TC patch validation

Artem Shutak
Cos, see email.

-- Artem --

On Thu, Oct 22, 2015 at 9:15 PM, Konstantin Boudnik <[hidden email]> wrote:

> On Thu, Oct 22, 2015 at 01:28PM, Artem Shutak wrote:
> > Yes, automatic runs were disabled for patches too.
> >
> > To run patches you can use "Run All for patch" with specified jira number
> > at "Paramethers / Jira number*".
>
> Right, that presumes that a user has an account. I am sure I have one, but
> I
> lost the password, because of the changes of the laptop and whatnot.
> There's
> no obvious name to reset it though; Artem could you help me to reset it and
> drop me a password separately or via skype?
>
> Thank you very much in advance!
>   Cos
>
> >
> > -- Artem --
> >
> > On Thu, Oct 22, 2015 at 4:11 AM, Dmitriy Setrakyan <
> [hidden email]>
> > wrote:
> >
> > > I think Cos’ question also was why the patches attached to Jira do not
> get
> > > automatically run on TC. To my knowledge, the automatic runs were
> disabled,
> > > but I am not sure if it includes patches as well.
> > >
> > > Can someone clarify how to run patches on TC?
> > >
> > > D.
> > >
> > > On Fri, Oct 16, 2015 at 2:16 AM, Ivan Veselovskiy <
> > > [hidden email]
> > > > wrote:
> > >
> > > > Hi, Konstantin,
> > > > Tests are grouped in suites by subsystems. You can run particular
> test
> > > > suite -- e.g. "Ignite Hadoop".
> > > > To run the tests with particular changes push the "Run..." button
> near
> > > that
> > > > test suite and chose "pull/<your-pull-request-number>/head" in "Build
> > > > branch" field on the "Changes" tab.
> > > >
> > > > On Fri, Oct 16, 2015 at 1:01 AM, Konstantin Boudnik <[hidden email]>
> > > > wrote:
> > > >
> > > > > Gents,
> > > > >
> > > > > is TC still picking up the JIRAs in PA state? Somehow it seems that
> > > only
> > > > > the
> > > > > latest changes from master are being picked.
> > > > >
> > > > > On a somewhat similar note: can I run tests for just a single
> module?
> > > > E.g.
> > > > > in
> > > > > IGNITE-1701 I made some changes in ignite-spark pom.xml and want to
> > > > quickly
> > > > > verify that this doesn't affect anything (which it shouldn't,
> clearly).
> > > > > Running the whole testset on my tiny laptop will probably take a
> few
> > > > hours.
> > > > >
> > > > > Appreciate any pointers, thanks in advance!
> > > > >   Cos
> > > > >
> > > > >
> > > >
> > >
>