Ignite Tests 2.4+ (Java 8) refactoring

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

Ignite Tests 2.4+ (Java 8) refactoring

vveider
Igniters,


As you may noticed, main test project is undergoing some refactoring;
namely, we are moving to architecture which is designed to reduce full tests
run time by introducing 'single-build / multiple tests' scheme: Apache
Ignite is built once and its artifacts are used in later parallel tests
execution (with no necessity to rebuild project for every test suite).

During the movement process, present test configurations will be replaced
one-by-one by their successor ones, preserving most of the settings (with
possible revision of some objectively odd parameters), so, please, do not be
afraid of '~[Obsolete]' prefix builds: they will be kept for about month for
the sake of every test run history. Also, be advised, that overall test
picture in project will be kept untouched 'cause it gathers info about run
test and not builds and aggregates it project wide. Your can continue to run
single builds as well as composite ones as part of the development process
as before.


As always, do no hesitate to ask questions or share your wishes concerning
this initiative.



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Reply | Threaded
Open this post in threaded view
|

Re: Ignite Tests 2.4+ (Java 8) refactoring

Dmitriy Pavlov
Hi Petr,

This is an important change in Ignite's testing process. Current and future
Igniters will be grateful for this change.

However, there may be a failure in tests 1) that were previously disabled
or 2) new infrastucture-related failures.

Any assistance with the identification each of type of fail is appreciated.

Sincerely,
Dmitriy Pavlov

чт, 22 мар. 2018 г. в 19:37, vveider <[hidden email]>:

> Igniters,
>
>
> As you may noticed, main test project is undergoing some refactoring;
> namely, we are moving to architecture which is designed to reduce full
> tests
> run time by introducing 'single-build / multiple tests' scheme: Apache
> Ignite is built once and its artifacts are used in later parallel tests
> execution (with no necessity to rebuild project for every test suite).
>
> During the movement process, present test configurations will be replaced
> one-by-one by their successor ones, preserving most of the settings (with
> possible revision of some objectively odd parameters), so, please, do not
> be
> afraid of '~[Obsolete]' prefix builds: they will be kept for about month
> for
> the sake of every test run history. Also, be advised, that overall test
> picture in project will be kept untouched 'cause it gathers info about run
> test and not builds and aggregates it project wide. Your can continue to
> run
> single builds as well as composite ones as part of the development process
> as before.
>
>
> As always, do no hesitate to ask questions or share your wishes concerning
> this initiative.
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite Tests 2.4+ (Java 8) refactoring

vveider
Of course, I check every new build several times until it gives the same results as obsolete one.



> On 22 Mar 2018, at 19:44, Dmitry Pavlov <[hidden email]> wrote:
>
> Hi Petr,
>
> This is an important change in Ignite's testing process. Current and future
> Igniters will be grateful for this change.
>
> However, there may be a failure in tests 1) that were previously disabled
> or 2) new infrastucture-related failures.
>
> Any assistance with the identification each of type of fail is appreciated.
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 22 мар. 2018 г. в 19:37, vveider <[hidden email]>:
>
>> Igniters,
>>
>>
>> As you may noticed, main test project is undergoing some refactoring;
>> namely, we are moving to architecture which is designed to reduce full
>> tests
>> run time by introducing 'single-build / multiple tests' scheme: Apache
>> Ignite is built once and its artifacts are used in later parallel tests
>> execution (with no necessity to rebuild project for every test suite).
>>
>> During the movement process, present test configurations will be replaced
>> one-by-one by their successor ones, preserving most of the settings (with
>> possible revision of some objectively odd parameters), so, please, do not
>> be
>> afraid of '~[Obsolete]' prefix builds: they will be kept for about month
>> for
>> the sake of every test run history. Also, be advised, that overall test
>> picture in project will be kept untouched 'cause it gathers info about run
>> test and not builds and aggregates it project wide. Your can continue to
>> run
>> single builds as well as composite ones as part of the development process
>> as before.
>>
>>
>> As always, do no hesitate to ask questions or share your wishes concerning
>> this initiative.
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>>