Folks,

Maybe I'm missing something, but what is the reason for setting
JAVA_HOME randomly? For instance, some commit is working under jdk8
but fails under jdk9 (and we declare that 9-th version is supported by
Ignite). Should we merge this commit to the master branch (all test
suites can be OK under jdk8)?

I know, that running all tests under all java version leads us to
Hell, but maybe we can have separated versions nightly builds?

On Wed, 19 Jun 2019 at 13:47, Павлухин Иван <vololo...@gmail.com> wrote:
>
> Dmitriy,
>
> Thank you for the hint! Java version seems to be the reason. I see
> that tests pass with Java 8 and 11 and fail with Java 10. See the
> exception below. Btw, do we test with Java 9? Have not seen that
> version in recent runs.
> java.lang.NoClassDefFoundError: javax/transaction/SystemException
>     at java.base/java.lang.Class.forName0(Native Method)
>     at java.base/java.lang.Class.forName(Class.java:291)
>     at 
> org.apache.ignite.internal.IgniteComponentType.createOptional0(IgniteComponentType.java:249)
>     at 
> org.apache.ignite.internal.IgniteComponentType.createOptional(IgniteComponentType.java:235)
>     at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.createSharedContext(GridCacheProcessor.java:3427)
>     at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.start(GridCacheProcessor.java:869)
>     at 
> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1886)
>     at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1135)
>     at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1992)
>     at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1683)
>     at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1109)
>     at 
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1027)
>     at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:913)
>     at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:812)
>     at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:682)
>     at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:651)
>     at org.apache.ignite.Ignition.start(Ignition.java:346)
>     at 
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:300)
> Caused by: java.lang.ClassNotFoundException: javax.transaction.SystemException
>     at 
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
>     at 
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:190)
>     at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
>     ... 18 more
>
> вт, 18 июн. 2019 г. в 23:27, Dmitriy Pavlov <dpav...@apache.org>:
> >
> > Hi Ivan,
> >
> > Can these failures be related to Java version? Java home is set randomly by
> > TC Bot.
> >
> > Dmitriy Pavlov
> >
> > вт, 18 июн. 2019 г. в 22:11, Павлухин Иван <vololo...@gmail.com>:
> >
> > > Hi igniters,
> > >
> > > Does anyone know why python, php and nodejs [1, 2, 3] suites fail so
> > > frequently on TC? Is there any activity to deal with it?
> > >
> > > [1]
> > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ThinClientPython&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
> > > [2]
> > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ThinClientNodeJs&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
> > > [3]
> > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ThinClientPhp&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
> > >
> > > --
> > > Best regards,
> > > Ivan Pavlukhin
> > >
>
>
>
> --
> Best regards,
> Ivan Pavlukhin

Reply via email to