Dmitry,
Sure, I've already informed author about this issue. Hope he will have time
to look at. I see no problems fixing it myself if fix will be simple. In
other
cases I doubt my ability of fixing complex .NET tests.
On Wed, 8 Aug 2018 at 19:08 Dmitriy Pavlov wrote:
> This change will
This change will trigger master every time if free agent percent >50%
longer than 10 minutes. And likelihood that was just one commit in each
runall is increased. But it is not 100% because several commit may be done
while TC was loaded.
Contributed change is not bisect based on git revisions,- I
Dmitry,
Good news.
How can I trigger build\MTCGA.Bot to find the problem commit?
As for this case I've already found commit who caused the test to fall.
I don't know how to fix this problem. Probably, we slould conslut with
author to find out the right case.
On Wed, 8 Aug 2018 at 18:29 Dmitriy
Ok, let's fill priority and version for new failures.
About locating changes, which break particular build:
Thanks to Pavel Pereslegin for his recent contribution to MTCGA.Bot. Patch
allows to adaptively trigger 'run all' in case there are enought of free
agents. So it will be easier to locate
Dmitriy, yes, if you set it as blocker and assign it to the next release,
the likelihood of someone looking at it before the release will increase.
We should follow this practice for all new test failures.
Moreover, if someone's change caused a new test failure, then we should try
to contact that
Hi Dmitriy,
Would it increase likelihood that somebody will pick up this ticket if we
will set blocker priority?
If it would increase I totally agree. IMO, JIRA priorities do not have much
effect on community members, do it?
Sincerely,
Dmitriy Pavlov
вт, 7 авг. 2018 г. в 14:00, Dmitriy
Dmitry,
I'm not familiar with all details of Ignite release management and can miss
something with changing the right issue priority. Hope you'll help me with
it at the initial stage. Generally, I agree with you here. I've marked this
issue as `Blocker` and attached to `2.7` release as this
Maxim, if it is a new failure, why is it filed as Minor and is not assigned
to any release? I would suggest that any new failure should be filed as a
Blocker and assigned to the next release.
D.
On Tue, Aug 7, 2018 at 12:55 AM, Maxim Muzafarov wrote:
> Igniters,
>
> Seems this is a new
Igniters,
Seems this is a new failures due to last changes.
I've created new issue [1].
[1] https://issues.apache.org/jira/browse/IGNITE-9202
On Fri, 3 Aug 2018 at 20:57 wrote:
> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I hope you
Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*New test failure in master
ExamplesTest.TestRemoteNodes(BinaryModeExample)
10 matches
Mail list logo
