Re: MTCGA: Tests of the week
Great progress, guys! Keep going! --Yakov
Re: MTCGA: Tests of the week
Great work! Best Regards, Igor On Tue, Mar 6, 2018 at 1:42 AM, Denis Magdawrote: > Astonishing progress! Thanks for keep driving this activity and making the > project more and more reliable. > > -- > Denis > > On Mon, Mar 5, 2018 at 1:47 PM, Dmitry Pavlov > wrote: > > > Hi, Denis, Igniters, > > > > I've updated the report for the last weekend mass run-all, please find it > > in wiki > > https://cwiki.apache.org/confluence/pages/viewpageattachments.action? > > pageId=73631266 > > > > In 30 clean runs, there was 371 failed tests, 21 suites. During previous > > mass run there were 804 tests including 355 C ++, suites 29. This > indicate > > progress, but still there is a lot of work to be done. > > > > Thanks to Alexey Goncharuk, Igor Sapego, and Maxim Muzafarov and all > folks > > were involved into this previous weeks. > > > > Sincerely, > > Dmitriy Pavlov > > > > вт, 27 февр. 2018 г. в 13:00, Dmitry Pavlov : > > > > > Hi Denis, > > > > > > It is not easy to say exact number of tests, because test failures are > > > quite randomized. Correct metric can be obtained from mass 'RunAll' > runs, > > > for example, during weekend. > > > > > > In the same time brief estimation gives number of failures around 30-60 > > > per 'RunAll' instead of 60-80 (we don't count 355 CPP test here because > > it > > > is one problem). > > > > > > If we check issues create/resolve chart, it is available > > > https://cwiki.apache.org/confluence/display/IGNITE/ > > Make+Teamcity+Green+Again, > > > progress is obivious, ~ 27 issues reported and ~ 13 were resolved. > > > > > > Hope someone in the community can pick up remaining unsassigned issues: > > > > > > https://issues.apache.org/jira/issues/?jql=labels% > > 3DMakeTeamcityGreenAgain%20AND%20createdDate%3E-3w% > > 20AND%20resolution%20is%20EMPTY%20and%20assignee%20is%20EMPTY > > > > > > Sincerely, > > > Dmitriy Pavlov > > > > > > > > > > > > вт, 27 февр. 2018 г. в 0:45, Denis Magda : > > > > > >> Hi Dmitriy, > > >> > > >> Could you share some statistics? How many tests were fixed or merged > in > > >> one? Just curiuos. > > >> > > >> -- > > >> Denis > > >> > > >> On Mon, Feb 26, 2018 at 9:36 AM, Dmitry Pavlov > > > >> wrote: > > >> > > >> > Hi Folks, > > >> > > > >> > Fixing the tests already brings some results. The number of falling > > >> tests > > >> > in a single run was reduced. Thanks to all, especially to Peter > > Ivanov, > > >> > Alexey Goncharuk, Pavel Kovalenko > > >> > > > >> > There are 4 tickets that were not picked up by community (list at > the > > >> end > > >> > of letter). Please look through and assign issue if you are able to > > help > > >> > with this. > > >> > > > >> > Sincerely, > > >> > Dmitriy Pavlov > > >> > > > >> > - IGNITE-7791 -Ignite Client Nodes: failed test > > >> > IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAnd > > Created() > > >> > - IGNITE-7789 - Ignite Client Nodes: failed test > > >> > IgniteClientReconnectApiExceptionTest.testErrorOnDisconnect() > > >> > - IGNITE-7708 - Ignite Compute has flaky failures in > > >> ConfigVariationTests > > >> > - IGNITE-7692 - affinityCall and affinityRun may execute code on > > backup > > >> > partitions > > >> > > > >> > > > > > >
Re: MTCGA: Tests of the week
Astonishing progress! Thanks for keep driving this activity and making the project more and more reliable. -- Denis On Mon, Mar 5, 2018 at 1:47 PM, Dmitry Pavlovwrote: > Hi, Denis, Igniters, > > I've updated the report for the last weekend mass run-all, please find it > in wiki > https://cwiki.apache.org/confluence/pages/viewpageattachments.action? > pageId=73631266 > > In 30 clean runs, there was 371 failed tests, 21 suites. During previous > mass run there were 804 tests including 355 C ++, suites 29. This indicate > progress, but still there is a lot of work to be done. > > Thanks to Alexey Goncharuk, Igor Sapego, and Maxim Muzafarov and all folks > were involved into this previous weeks. > > Sincerely, > Dmitriy Pavlov > > вт, 27 февр. 2018 г. в 13:00, Dmitry Pavlov : > > > Hi Denis, > > > > It is not easy to say exact number of tests, because test failures are > > quite randomized. Correct metric can be obtained from mass 'RunAll' runs, > > for example, during weekend. > > > > In the same time brief estimation gives number of failures around 30-60 > > per 'RunAll' instead of 60-80 (we don't count 355 CPP test here because > it > > is one problem). > > > > If we check issues create/resolve chart, it is available > > https://cwiki.apache.org/confluence/display/IGNITE/ > Make+Teamcity+Green+Again, > > progress is obivious, ~ 27 issues reported and ~ 13 were resolved. > > > > Hope someone in the community can pick up remaining unsassigned issues: > > > > https://issues.apache.org/jira/issues/?jql=labels% > 3DMakeTeamcityGreenAgain%20AND%20createdDate%3E-3w% > 20AND%20resolution%20is%20EMPTY%20and%20assignee%20is%20EMPTY > > > > Sincerely, > > Dmitriy Pavlov > > > > > > > > вт, 27 февр. 2018 г. в 0:45, Denis Magda : > > > >> Hi Dmitriy, > >> > >> Could you share some statistics? How many tests were fixed or merged in > >> one? Just curiuos. > >> > >> -- > >> Denis > >> > >> On Mon, Feb 26, 2018 at 9:36 AM, Dmitry Pavlov > >> wrote: > >> > >> > Hi Folks, > >> > > >> > Fixing the tests already brings some results. The number of falling > >> tests > >> > in a single run was reduced. Thanks to all, especially to Peter > Ivanov, > >> > Alexey Goncharuk, Pavel Kovalenko > >> > > >> > There are 4 tickets that were not picked up by community (list at the > >> end > >> > of letter). Please look through and assign issue if you are able to > help > >> > with this. > >> > > >> > Sincerely, > >> > Dmitriy Pavlov > >> > > >> > - IGNITE-7791 -Ignite Client Nodes: failed test > >> > IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAnd > Created() > >> > - IGNITE-7789 - Ignite Client Nodes: failed test > >> > IgniteClientReconnectApiExceptionTest.testErrorOnDisconnect() > >> > - IGNITE-7708 - Ignite Compute has flaky failures in > >> ConfigVariationTests > >> > - IGNITE-7692 - affinityCall and affinityRun may execute code on > backup > >> > partitions > >> > > >> > > >
Re: MTCGA: Tests of the week
Hi, Denis, Igniters, I've updated the report for the last weekend mass run-all, please find it in wiki https://cwiki.apache.org/confluence/pages/viewpageattachments.action?pageId=73631266 In 30 clean runs, there was 371 failed tests, 21 suites. During previous mass run there were 804 tests including 355 C ++, suites 29. This indicate progress, but still there is a lot of work to be done. Thanks to Alexey Goncharuk, Igor Sapego, and Maxim Muzafarov and all folks were involved into this previous weeks. Sincerely, Dmitriy Pavlov вт, 27 февр. 2018 г. в 13:00, Dmitry Pavlov: > Hi Denis, > > It is not easy to say exact number of tests, because test failures are > quite randomized. Correct metric can be obtained from mass 'RunAll' runs, > for example, during weekend. > > In the same time brief estimation gives number of failures around 30-60 > per 'RunAll' instead of 60-80 (we don't count 355 CPP test here because it > is one problem). > > If we check issues create/resolve chart, it is available > https://cwiki.apache.org/confluence/display/IGNITE/Make+Teamcity+Green+Again, > progress is obivious, ~ 27 issues reported and ~ 13 were resolved. > > Hope someone in the community can pick up remaining unsassigned issues: > > https://issues.apache.org/jira/issues/?jql=labels%3DMakeTeamcityGreenAgain%20AND%20createdDate%3E-3w%20AND%20resolution%20is%20EMPTY%20and%20assignee%20is%20EMPTY > > Sincerely, > Dmitriy Pavlov > > > > вт, 27 февр. 2018 г. в 0:45, Denis Magda : > >> Hi Dmitriy, >> >> Could you share some statistics? How many tests were fixed or merged in >> one? Just curiuos. >> >> -- >> Denis >> >> On Mon, Feb 26, 2018 at 9:36 AM, Dmitry Pavlov >> wrote: >> >> > Hi Folks, >> > >> > Fixing the tests already brings some results. The number of falling >> tests >> > in a single run was reduced. Thanks to all, especially to Peter Ivanov, >> > Alexey Goncharuk, Pavel Kovalenko >> > >> > There are 4 tickets that were not picked up by community (list at the >> end >> > of letter). Please look through and assign issue if you are able to help >> > with this. >> > >> > Sincerely, >> > Dmitriy Pavlov >> > >> > - IGNITE-7791 -Ignite Client Nodes: failed test >> > IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated() >> > - IGNITE-7789 - Ignite Client Nodes: failed test >> > IgniteClientReconnectApiExceptionTest.testErrorOnDisconnect() >> > - IGNITE-7708 - Ignite Compute has flaky failures in >> ConfigVariationTests >> > - IGNITE-7692 - affinityCall and affinityRun may execute code on backup >> > partitions >> > >> >
Re: MTCGA: Tests of the week
Hi Denis, It is not easy to say exact number of tests, because test failures are quite randomized. Correct metric can be obtained from mass 'RunAll' runs, for example, during weekend. In the same time brief estimation gives number of failures around 30-60 per 'RunAll' instead of 60-80 (we don't count 355 CPP test here because it is one problem). If we check issues create/resolve chart, it is available https://cwiki.apache.org/confluence/display/IGNITE/Make+Teamcity+Green+Again, progress is obivious, ~ 27 issues reported and ~ 13 were resolved. Hope someone in the community can pick up remaining unsassigned issues: https://issues.apache.org/jira/issues/?jql=labels%3DMakeTeamcityGreenAgain%20AND%20createdDate%3E-3w%20AND%20resolution%20is%20EMPTY%20and%20assignee%20is%20EMPTY Sincerely, Dmitriy Pavlov вт, 27 февр. 2018 г. в 0:45, Denis Magda: > Hi Dmitriy, > > Could you share some statistics? How many tests were fixed or merged in > one? Just curiuos. > > -- > Denis > > On Mon, Feb 26, 2018 at 9:36 AM, Dmitry Pavlov > wrote: > > > Hi Folks, > > > > Fixing the tests already brings some results. The number of falling tests > > in a single run was reduced. Thanks to all, especially to Peter Ivanov, > > Alexey Goncharuk, Pavel Kovalenko > > > > There are 4 tickets that were not picked up by community (list at the end > > of letter). Please look through and assign issue if you are able to help > > with this. > > > > Sincerely, > > Dmitriy Pavlov > > > > - IGNITE-7791 -Ignite Client Nodes: failed test > > IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated() > > - IGNITE-7789 - Ignite Client Nodes: failed test > > IgniteClientReconnectApiExceptionTest.testErrorOnDisconnect() > > - IGNITE-7708 - Ignite Compute has flaky failures in ConfigVariationTests > > - IGNITE-7692 - affinityCall and affinityRun may execute code on backup > > partitions > > >
Re: MTCGA: Tests of the week
Hi Dmitriy, Could you share some statistics? How many tests were fixed or merged in one? Just curiuos. -- Denis On Mon, Feb 26, 2018 at 9:36 AM, Dmitry Pavlovwrote: > Hi Folks, > > Fixing the tests already brings some results. The number of falling tests > in a single run was reduced. Thanks to all, especially to Peter Ivanov, > Alexey Goncharuk, Pavel Kovalenko > > There are 4 tickets that were not picked up by community (list at the end > of letter). Please look through and assign issue if you are able to help > with this. > > Sincerely, > Dmitriy Pavlov > > - IGNITE-7791 -Ignite Client Nodes: failed test > IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated() > - IGNITE-7789 - Ignite Client Nodes: failed test > IgniteClientReconnectApiExceptionTest.testErrorOnDisconnect() > - IGNITE-7708 - Ignite Compute has flaky failures in ConfigVariationTests > - IGNITE-7692 - affinityCall and affinityRun may execute code on backup > partitions >
MTCGA: Tests of the week
Hi Folks, Fixing the tests already brings some results. The number of falling tests in a single run was reduced. Thanks to all, especially to Peter Ivanov, Alexey Goncharuk, Pavel Kovalenko There are 4 tickets that were not picked up by community (list at the end of letter). Please look through and assign issue if you are able to help with this. Sincerely, Dmitriy Pavlov - IGNITE-7791 -Ignite Client Nodes: failed test IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated() - IGNITE-7789 - Ignite Client Nodes: failed test IgniteClientReconnectApiExceptionTest.testErrorOnDisconnect() - IGNITE-7708 - Ignite Compute has flaky failures in ConfigVariationTests - IGNITE-7692 - affinityCall and affinityRun may execute code on backup partitions