[MTCGA]: new failures in builds [1492655] needs to be handled
Hi Ignite Developer, I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I hope you can help. *New Critical Failure in master PDS 1 https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Pds1=%3Cdefault%3E=buildTypeStatusDiv No changes in build - If your changes can led to this failure(s), please create issue with label MakeTeamCityGreenAgain and assign it to you. -- If you have fix, please set ticket to PA state and write to dev list fix is ready -- For case fix will require some time please mute test and set label Muted_Test to issue - If you know which change caused failure please contact change author directly - If you don't know which change caused failure please send message to dev list to find out Should you have any questions please contact dpav...@apache.org or write to dev.list Best Regards, MTCGA.Bot Notification generated at Sun Jul 29 03:12:41 MSK 2018
[GitHub] ignite pull request #4451: Add missed property descriptions for DataRegionMe...
GitHub user laz2 opened a pull request: https://github.com/apache/ignite/pull/4451 Add missed property descriptions for DataRegionMetricsMXBean You can merge this pull request into a Git repository by running: $ git pull https://github.com/laz2/ignite data-region-metrics-missing-mx-desc Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4451.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4451 commit c2ade44b8e5c55c5ad76bc7c95f9872885fde09e Author: Dmitry Lazurkin Date: 2018-07-28T20:30:30Z Add missed property descriptions for DataRegionMetricsMXBean ---
Re: [jira] [Assigned] (IGNITE-9113) Allocate memory for a data region when first cache assigned to this region is created
On Sat, Jul 28, 2018 at 2:20 AM, Dmitriy Pavlov wrote: > Hi Dmitriy, > > As far as I know this approach is contlicting with the Apache Way. We > should be absolutely sure that assignee is agree and going to do this task. > But in our case domain expert did not replied to dev list topic. > I do not see any conflict with any Apache rule at all. By assigning a ticket to someone I am suggesting that as a domain expert it is preferable that he or she looks at it. If not, these people can un-assign or reassign the ticket. If you believe there is a conflict with some Apache principle, please provide a link so we could all learn about it. To solve lost ticket problem I suggest to use dev. list and bumping up/ping > messages. > Agree, I do that too. > I hope it makes sense to you. If not, I will do my absolute best to find > out corresponding ASF policy. > Please do. > > Sincerely, > Dmitriy Pavlov > > сб, 28 июл. 2018 г. в 3:28, Dmitriy Setrakyan : > > > On Fri, Jul 27, 2018 at 3:02 PM, Dmitriy Pavlov > > wrote: > > > > > Hi Igniters, > > > > > > I would discourage all Igniters from direct assigning issues to anyone > > > else. Of cource excepting the case it was directly discussed with > > asignee. > > > Any contributor should be able to assign issue to himself. > > > > > > I left issue unassigned until Alex G would assign it. > > > > > > > Dmitriy, I disagree. If there is a domain expert, then the issue should > be > > assigned to him/her whenever possible. If that person is too busy, he/she > > could ask someone else for help. This way the tickets will get attention > > faster and will get resolved faster. > > > > https://issues.apache.org/jira/browse/IGNITE-9113 > > > > D. > > >
[GitHub] ignite pull request #4341: Act deact to
Github user Mmuzaf closed the pull request at: https://github.com/apache/ignite/pull/4341 ---
[GitHub] ignite pull request #4450: fix timeout.
GitHub user BiryukovVA opened a pull request: https://github.com/apache/ignite/pull/4450 fix timeout. You can merge this pull request into a Git repository by running: $ git pull https://github.com/BiryukovVA/ignite timeout_zk_suite Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4450.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4450 commit e8a8dbd34a68b267b217d86e958962193d899146 Author: Vitaliy Biryukov Date: 2018-07-27T10:03:19Z fix timeout. ---
Re: [jira] [Assigned] (IGNITE-9113) Allocate memory for a data region when first cache assigned to this region is created
Hi Dmitriy, As far as I know this approach is contlicting with the Apache Way. We should be absolutely sure that assignee is agree and going to do this task. But in our case domain expert did not replied to dev list topic. To solve lost ticket probem I suggest to use dev. list and bumping up/ping messages. I hope it makes sense to you. If not, I will do my absolute best to find out corresponding ASF policy. Sincerely, Dmitriy Pavlov сб, 28 июл. 2018 г. в 3:28, Dmitriy Setrakyan : > On Fri, Jul 27, 2018 at 3:02 PM, Dmitriy Pavlov > wrote: > > > Hi Igniters, > > > > I would discourage all Igniters from direct assigning issues to anyone > > else. Of cource excepting the case it was directly discussed with > asignee. > > Any contributor should be able to assign issue to himself. > > > > I left issue unassigned until Alex G would assign it. > > > > Dmitriy, I disagree. If there is a domain expert, then the issue should be > assigned to him/her whenever possible. If that person is too busy, he/she > could ask someone else for help. This way the tickets will get attention > faster and will get resolved faster. > > https://issues.apache.org/jira/browse/IGNITE-9113 > > D. >
