yeah, i will чт, 9 февр. 2017 г. в 0:01, Denis Magda <dma...@apache.org>:
> > How could they co-exist ? When you developing some ticket you are risking > > introduce bug which is reproduced by already failed test(s). > > Because there is no IT project that is bug-free. In my experience, it’s a > usual situation when a part of the system is being evolved while the other > is being fixed - this is why both feature development & bug fixing co-exist. > > In any case, I do believe that most of the tests that fail used to be > sporadic ones when a modification was applied and a contributor had been > validating his changes. These casual failures can easily lead to the > situation when the contributor commits the changes that introduce new bugs. > > We should have JIRA tickets for most of the test failures: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20Ignite%20and%20summary~%22test%22%20and%20status%20!%3D%20closed > < > https://issues.apache.org/jira/issues/?jql=project%20=%20Ignite%20and%20summary~%22test%22%20and%20status%20!=%20closed > > > > Would you be interested picking some of them making the product more > stable? Basically, this should help your the internals even more profoundly. > > — > Denis > > > On Feb 7, 2017, at 11:50 PM, ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com> > wrote: > > > > How could they co-exist ? When you developing some ticket you are risking > > introduce bug which is reproduced by already failed test(s). > > Moreover its time consuming to look up new failed tests when your build > has > > completed. > > The last one, committers who introduced new bugs is responsible for them > > and have to fix them, not other ones. > > There are number of tests which i have to execute to ensure they are > flaky > > or permanently failed. For example this one : > > CacheJdbcPojoStoreTest.testLoadCache() > > > > > > > > вт, 7 февр. 2017 г. в 22:10, Denis Magda <dma...@apache.org>: > > > >> Aleksey, > >> > >> Bugs fixing and features development are two processes that usually > >> co-exist. > >> > >> Some of the committer/contributors fix tests/functionality while the > >> others add new functionality. Someone does both. > >> > >> You’re welcomed to start fixing the failing tests. Are there any > specific > >> that annoys you most? > >> > >> — > >> Denis > >> > >>> On Feb 7, 2017, at 8:40 AM, ALEKSEY KUZNETSOV < > alkuznetsov...@gmail.com> > >> wrote: > >>> > >>> We have a lot of failed tests, which is frustrating. Some of them are > >>> flaky(floating status randomly goes from succesful to failed) which > adds > >> to > >>> frustration. Perhaps, we should fix all the tests in first place, and > >> then > >>> continue doing tickets ? > >>> -- > >>> > >>> *Best Regards,* > >>> > >>> *Kuznetsov Aleksey* > >> > >> -- > > > > *Best Regards,* > > > > *Kuznetsov Aleksey* > > -- *Best Regards,* *Kuznetsov Aleksey*
