Test 150 clients migrated to `Cache [6]` suite

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

Test 150 clients migrated to `Cache [6]` suite

Dmitrii Ryabov
Hello Igniters!



I migrated test `IgniteCache150ClientsTest` from `150 Clients` suite to `
Cache [6]`, because `150 Clients` contains only one test class and makes
~6min excess Ignite build.



So, test suites `150 Clients` and `~[Obsolete] 150 Clients` will be deleted
 soon.
Reply | Threaded
Open this post in threaded view
|

Re: Test 150 clients migrated to `Cache [6]` suite

vveider
Nice work!


Yet, I have to ask to keep '~[Obsolete] 150 Clients’ build configuration for at least month from latest run until its build history is removed by autoclean — it’ll be nice to keep that test history.



> On 23 Mar 2018, at 11:53, Дмитрий Рябов <[hidden email]> wrote:
>
> Hello Igniters!
>
>
>
> I migrated test `IgniteCache150ClientsTest` from `150 Clients` suite to `
> Cache [6]`, because `150 Clients` contains only one test class and makes
> ~6min excess Ignite build.
>
>
>
> So, test suites `150 Clients` and `~[Obsolete] 150 Clients` will be deleted
> soon.

Reply | Threaded
Open this post in threaded view
|

Re: Test 150 clients migrated to `Cache [6]` suite

Dmitriy Pavlov
Hi Dmitriy,

  Thank you for this improvement.

Hi Petr,

  IMO there is no need to keep Obsolete suites for so long time because
Igniters ususally do not use test history (excepting TC Jedi who helps with
monitoring). Moreover, test history itself is global, so still no need to
keep suites too long time.

I think it is reasonable to notify before changes because someone may have
created unique parameters combination in suite, so it is not desirable to
delete it without notification (as it was for zIgnores & reproducing
suite).

So let's wait for some time for objections, and if noone objects, we'll
remove.

Sincerely,
Dmitriy Pavlov

пт, 23 мар. 2018 г. в 12:07, Petr Ivanov <[hidden email]>:

> Nice work!
>
>
> Yet, I have to ask to keep '~[Obsolete] 150 Clients’ build configuration
> for at least month from latest run until its build history is removed by
> autoclean — it’ll be nice to keep that test history.
>
>
>
> > On 23 Mar 2018, at 11:53, Дмитрий Рябов <[hidden email]> wrote:
> >
> > Hello Igniters!
> >
> >
> >
> > I migrated test `IgniteCache150ClientsTest` from `150 Clients` suite to `
> > Cache [6]`, because `150 Clients` contains only one test class and makes
> > ~6min excess Ignite build.
> >
> >
> >
> > So, test suites `150 Clients` and `~[Obsolete] 150 Clients` will be
> deleted
> > soon.
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Test 150 clients migrated to `Cache [6]` suite

vveider
No objections then.



> On 23 Mar 2018, at 13:03, Dmitry Pavlov <[hidden email]> wrote:
>
> Hi Dmitriy,
>
>  Thank you for this improvement.
>
> Hi Petr,
>
>  IMO there is no need to keep Obsolete suites for so long time because
> Igniters ususally do not use test history (excepting TC Jedi who helps with
> monitoring). Moreover, test history itself is global, so still no need to
> keep suites too long time.
>
> I think it is reasonable to notify before changes because someone may have
> created unique parameters combination in suite, so it is not desirable to
> delete it without notification (as it was for zIgnores & reproducing
> suite).
>
> So let's wait for some time for objections, and if noone objects, we'll
> remove.
>
> Sincerely,
> Dmitriy Pavlov
>
> пт, 23 мар. 2018 г. в 12:07, Petr Ivanov <[hidden email]>:
>
>> Nice work!
>>
>>
>> Yet, I have to ask to keep '~[Obsolete] 150 Clients’ build configuration
>> for at least month from latest run until its build history is removed by
>> autoclean — it’ll be nice to keep that test history.
>>
>>
>>
>>> On 23 Mar 2018, at 11:53, Дмитрий Рябов <[hidden email]> wrote:
>>>
>>> Hello Igniters!
>>>
>>>
>>>
>>> I migrated test `IgniteCache150ClientsTest` from `150 Clients` suite to `
>>> Cache [6]`, because `150 Clients` contains only one test class and makes
>>> ~6min excess Ignite build.
>>>
>>>
>>>
>>> So, test suites `150 Clients` and `~[Obsolete] 150 Clients` will be
>> deleted
>>> soon.
>>
>>

Reply | Threaded
Open this post in threaded view
|

Re: Test 150 clients migrated to `Cache [6]` suite

Dmitriy Pavlov
Hi Igniters,

I've deleted this run config.

Sincerely,
Dmitriy Pavlov

пт, 23 мар. 2018 г. в 13:50, Petr Ivanov <[hidden email]>:

> No objections then.
>
>
>
> > On 23 Mar 2018, at 13:03, Dmitry Pavlov <[hidden email]> wrote:
> >
> > Hi Dmitriy,
> >
> >  Thank you for this improvement.
> >
> > Hi Petr,
> >
> >  IMO there is no need to keep Obsolete suites for so long time because
> > Igniters ususally do not use test history (excepting TC Jedi who helps
> with
> > monitoring). Moreover, test history itself is global, so still no need to
> > keep suites too long time.
> >
> > I think it is reasonable to notify before changes because someone may
> have
> > created unique parameters combination in suite, so it is not desirable to
> > delete it without notification (as it was for zIgnores & reproducing
> > suite).
> >
> > So let's wait for some time for objections, and if noone objects, we'll
> > remove.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пт, 23 мар. 2018 г. в 12:07, Petr Ivanov <[hidden email]>:
> >
> >> Nice work!
> >>
> >>
> >> Yet, I have to ask to keep '~[Obsolete] 150 Clients’ build configuration
> >> for at least month from latest run until its build history is removed by
> >> autoclean — it’ll be nice to keep that test history.
> >>
> >>
> >>
> >>> On 23 Mar 2018, at 11:53, Дмитрий Рябов <[hidden email]> wrote:
> >>>
> >>> Hello Igniters!
> >>>
> >>>
> >>>
> >>> I migrated test `IgniteCache150ClientsTest` from `150 Clients` suite
> to `
> >>> Cache [6]`, because `150 Clients` contains only one test class and
> makes
> >>> ~6min excess Ignite build.
> >>>
> >>>
> >>>
> >>> So, test suites `150 Clients` and `~[Obsolete] 150 Clients` will be
> >> deleted
> >>> soon.
> >>
> >>
>
>