Hi!
Yes, now it's a part of the Travis check, and there is already a first
successful build [1]. But I think it's also required to run the check on TC
too, along with jobs for checking licenses, code style, and core
inspections.
[1] https://travis-ci.com/github/apache/ignite/builds/216363067
Hello Ilya !
>Hello!
>
>In the test GridDifferentLocalDeploymentSelfTest, I can see that some count
>of internal data structure yanked from a class field is not equal expected
>(without the fix).
GridDifferentLocalDeploymentSelfTest checks that inner deployment machinery are
not «leak» the
Hi Igniters,
Feb 10 is the due date for submitting the next board report. I would like
to submit it a bit earlier, by the end of the day on Feb 9.
Here is the first version of the report (at the end of the email). Should
we add here something important?
What do you think if it worths
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
As previously agreed, ticket [1], examples of concurrent tests you can find
here GridDifferentLocalDeploymentSelfTest and here
IgniteExplicitImplicitDeploymentSelfTest , TC in progress. Fabric — possibly i
mention incorrect word here, more clear it need to be — factory )
I suppose additional
