Hello! There is no scenario where you would run all tests during mvn clean install.
Normally, tests are run on per test suite basis with specific suite settings. It will make more than a day to run all tests and they might interfere each other. The proper way of running tests is ci.ignite.apache.org which should be available to all contributors (I think). You should ask to be a contributor on developers list. So the realistic way to build Ignite is -DskipTests. OR, -DfailIfNoTests=false -Dtest=SpecificClassTest. Regards, -- Ilya Kasnacheev пн, 3 дек. 2018 г. в 14:54, Namrata Bhave <[email protected]>: > Hi, > > > > I have recently started working with Apache Ignite. Build on x86 Ubuntu > 16.04 is complete. However, while running tests using `mvn test` command, > the execution gets stuck while running `ignite-core` module. > > Hence started running tests on individual modules, where similar behavior > was seen in ignite-indexing, ignite-clients and ignite-ml modules as well. > > I have tried setting JAVA heap settings, running on a system with 32GB > RAM. > > Is there a way to avoid this and get complete test results? Also, is there > any CI or such environment where I can get results of unit tests? > > > > Would appreciate any help provided. > > > > Thanks and Regards, > > Namrata >
