[jira] [Created] (IGNITE-12071) Test failures after IGNITE-9562 fix

Dmitriy Pavlov created IGNITE-12071: --- Summary: Test failures after IGNITE-9562 fix Key: IGNITE-12071 URL: https://issues.apache.org/jira/browse/IGNITE-12071 Project: Ignite Issue Type

[jira] [Created] (IGNITE-8604) .NET test failures probably after IGNITE-5789 merge

Dmitriy Pavlov created IGNITE-8604: -- Summary: .NET test failures probably after IGNITE-5789 merge Key: IGNITE-8604 URL: https://issues.apache.org/jira/browse/IGNITE-8604 Project: Ignite

Re: New test failures in .NET

not that hard. > > > > Thank you, > > Pavel > > > > > > > > [1] https://github.com/apache/ignite/commit/70ca86a30a7589f9ff46 > > 6b93a958362135347d02 > > > > > > > > On Fri, Mar 16, 2018 at 2:51 PM, Dmitry Pavlov <dpa

Re: New test failures in .NET

d. > > Thank you, > Pavel > > > > [1] https://github.com/apache/ignite/commit/70ca86a30a7589f9ff46 > 6b93a958362135347d02 > > > > On Fri, Mar 16, 2018 at 2:51 PM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: > > > Hi, > > > &g

Re: New test failures in .NET

k you, > Pavel > > > > [1] https://github.com/apache/ignite/commit/70ca86a30a7589f9ff46 > 6b93a958362135347d02 > > > > On Fri, Mar 16, 2018 at 2:51 PM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: > > > Hi, > > > > There a

Re: New test failures in .NET

t for your fellow Igniters and verify changes on TeamCity before merging. It is not that hard. Thank you, Pavel [1] https://github.com/apache/ignite/commit/70ca86a30a7589f9ff46 6b93a958362135347d02 On Fri, Mar 16, 2018 at 2:51 PM, Dmitry Pavlov <dpavlov@gmail.com> wrote: > Hi, &g

New test failures in .NET

Hi, There are 31 test failures in .NET tests https://ci.ignite.apache.org/viewLog.html?buildId=1137460=buildResultsDiv=IgniteTests24Java8_IgnitePlatformNet Unfortunately it continues to reproduce. Igniters, who can advice how to fix it? Was there any changes in .NET tests/new tests

[GitHub] ignite pull request #3557: IGNITE-7763: Fixed C++ Win32 test failures

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3557 ---

[GitHub] ignite pull request #3557: IGNITE-7763: Fixed C++ Win32 test failures

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/3557 IGNITE-7763: Fixed C++ Win32 test failures You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7763 Alternatively

[jira] [Created] (IGNITE-7675) Ignite Hadoop: test failures: "Stream has been closed: IgfsOutputStreamImpl"

Dmitriy Pavlov created IGNITE-7675: -- Summary: Ignite Hadoop: test failures: "Stream has been closed: IgfsOutputStreamImpl" Key: IGNITE-7675 URL: https://issues.apache.org/jira/browse/I

Re: Test failures

ification 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://is

Re: Test failures

I also agree. I think we should create tickets for all failing tests and have the community grab them. On Wed, Feb 8, 2017 at 5:50 AM, Александр Меньшиков wrote: > +1 to Aleksey, Alexander and Vyacheslav. > > I suppose that the best option is make issue for every

Re: Test failures

+1 to Aleksey, Alexander and Vyacheslav. I suppose that the best option is make issue for every master-failed-test. And fix them all. Floating tests should be normal. I think in most case we can just add repeating. All new test for some not ready future should be marked like "Should be fix in

Re: Test failures

I vote for the master-branche without failed-tests) I understand that impossible to make it quickly. We shall aim at this approach. It will be more comfortable to us to develop. 2017-02-08 12:17 GMT+03:00 Alexander Fedotov : > Hi, > > I would agree with Aleksey.

Re: Test failures

Hi, I would agree with Aleksey. >From the CI perspective, failing tests should be the main concern, because it prevents a durable development of new features. Also, as Aleksey has noted, developers working on different features could end up fixing the same regressions, chances are - in different

Re: Test failures

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

Re: Test failures

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

Test failures

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*