Re: [MTCGA]: new failures in builds [1662343] needs to be handled

Hi, I've looked at the issue and propose a patch. Review it, please. Vyacheslav, could you, please, assist with getting TC results, to be sure that tests passed well. Best regards, Aleksei Zaitsev 16.08.2018, 18:52, "Dmitriy Pavlov" : > Hi, > > I've failed h

Re: Ignite contibutors page

Hello Denis, Could you, please, add me to the list too: alexzaitzev (Aleksei Zaitsev). https://ignite.apache.org/community/resources.html Thanks. Best regards, Alex. 15.03.2018, 21:03, "Denis Magda" : > Dmitriy, Alexey, > > Done, now your names are engraved on the pag

Re: New Compatibility Testing Framework module in the project

ly, > Dmitriy Pavlov > > пн, 30 окт. 2017 г. в 10:06, Aleksei Zaitsev : > >>  Thanks, Dmitry, but why wiki and not readme.io[1]? It has a section "Test >>  and benchmarking", which suits well for such information. >> >>  I thought, that wiki is deprecate

Re: New Compatibility Testing Framework module in the project

Thanks, Dmitry, but why wiki and not readme.io[1]? It has a section "Test and benchmarking", which suits well for such information. I thought, that wiki is deprecated source of documentation. Correct me if I am wrong. [1] https://apacheignite.readme.io/docs 27.10.2017, 20:29, "Dmitry Pavlov" :

Mockito 1.9.5 and JUnit 4.11 incompatibility

Hi, guys. There is a known issue, that mockito 1.9.5 and JUnit 4.11 are not compatible: https://code.google.com/archive/p/mockito/issues/397 In our project we have these versions of libraries, so when someone wants to write "red" unit test, like this one: import org.junit.Test; import static o

Re: Binary compatibility of persistent storage

I vote for the 4th variant, because it is the most common approach to the versioning. For example, SemVer says that you can make incompatible API changes only in major versions. 19.09.2017, 14:52, "Vladimir Ozerov" : > Yakov, > > Any major change in data/index page format. E.g. this could happe

Ignite Benchmarking Rules

Hi, Igniters. Recently I’ve done some research in benchmarks for Ignite, and noticed that we don’t have any rules for running benchmarks and collecting result from them. Although sometimes we have tasks, which results need to be measured. I propose to formalize such things as: * set of benchma

Re: Ignite Benchmarking page on readme.io

t; On Thu, Sep 7, 2017 at 8:26 AM, Anton Vinogradov > wrote: >> Aleksei, >> >> Good idea. >> Could you please prepare page in MD format and attach link to branch >> containing it to the issue to review before publication? >> >> On Thu, Sep 7, 2017 at 1:45 PM, Ale

Ignite Benchmarking page on readme.io

Hi, guys. Issue[1] stated that we have not any information about Apache Ignite benchmarking on our site https://apacheignite.readme.io. I want to add such a page, but I can’t find appropriate section for it. I suggest to make new section named ‘Tests and Benchmarking’ and put all information ab

Re: Yardstick framework for Ignite 2.1

> On Mon, Sep 4, 2017 at 6:12 PM, Dmitriy Setrakyan > wrote: > >>  Guys, if the code is wrong, let's remove it and add a warning on the >>  readme.md clearly stating where to go for the correct benchmarks. >> >>  Also, huge +1 for adding benchmarking p

[jira] [Created] (IGNITE-6278) Add benchmarking page to readme.io

Aleksei Zaitsev created IGNITE-6278: --- Summary: Add benchmarking page to readme.io Key: IGNITE-6278 URL: https://issues.apache.org/jira/browse/IGNITE-6278 Project: Ignite Issue Type: Wish

Re: Yardstick framework for Ignite 2.1

ing. I think it's not critical, so let's do it in any of the discussed ways. 04.09.2017, 13:42, "Anton Vinogradov" : > Aleksei, > > I see a lot of removals, not a warning. > > On Mon, Sep 4, 2017 at 2:18 PM, Aleksei Zaitsev > wrote: > >>  >> I

Re: Yardstick framework for Ignite 2.1

gt;  > > > > I think this repository useful if I want just run benchmark and >>  play >>  > > with >>  > > > > them. Downloading binary distribution (or checkout whole Apache >>  > Ignite >>  > > > > source) fo

Re: Yardstick framework for Ignite 2.1

hat some code was removed. Are we offering to users to > try the benchmarks shipped with Ignite instead? > > On Wed, Aug 30, 2017 at 7:40 PM, Aleksei Zaitsev > wrote: > >>  Have done just like we discussed. >> >>  PR: https://github.com/apacheignite/yardstick-ig

Re: Yardstick framework for Ignite 2.1

ctly. > > On Wed, Aug 23, 2017 at 7:40 AM, Aleksei Zaitsev > wrote: > >>  Yes, we can, but then we will have to do it after each release. Maybe it's >>  better to add information in yardstick repo README, that Apache Ignite >>  contains benchmarks since versio

[jira] [Created] (IGNITE-6227) Delete obsolete benchmarks for Ignite 1.9

Aleksei Zaitsev created IGNITE-6227: --- Summary: Delete obsolete benchmarks for Ignite 1.9 Key: IGNITE-6227 URL: https://issues.apache.org/jira/browse/IGNITE-6227 Project: Ignite Issue Type

Re: Yardstick framework for Ignite 2.1

Yes, we can, but then we will have to do it after each release. Maybe it's better to add information in yardstick repo README, that Apache Ignite contains benchmarks since version 2.0? 22.08.2017, 16:55, "Dmitriy Setrakyan" : > On Tue, Aug 22, 2017 at 7:19 AM, Aleksei Zaitsev

Re: Yardstick framework for Ignite 2.1

> > Thoughts? > > D. > > On Mon, Aug 21, 2017 at 7:14 AM, Aleksei Zaitsev > wrote: > >>  Thanks, looks like that's what I need. >> >>  21.08.2017, 12:17, "Nikolai Tikhonov" : >>  > Hello, >>  > >>  > Yes, this re

Re: Yardstick framework for Ignite 2.1

Thanks, looks like that's what I need. 21.08.2017, 12:17, "Nikolai Tikhonov" : > Hello, > > Yes, this repository contains benchmarks for old Apache Ignite and > yardstick version. The last versions Apache Ignite distributed with > benchmarks. You can download there > https://ignite.apache.org/down