FYI
I found out how a Java version and addinional java module parameters
are passed to a build after choosing jdk version in a "Run custom
build" dialog.
A version is controlled by a reverse.dep.*.env.JAVA_HOME configuration
parameter specified to behave like a combobox in a "~[Obsolete] Run
test
After a little bit more experimentation I tend to think that adding
java.transaction module is not needed and even brings a negative
effect. E.g. if we use an ignite binary release and enable optional
jta module (by copying libraries to lib folder) then a node simply
fails to start (failing to reso
My next question is why do we need adding java.transaction module
explicitly for Java 9 and 10? As I see since 11 version there is no
such module and classes from it in modules bundled with JDK. So, I
suppose either we do not need java.transaction module or something
does not work with Java 11. It
Igniters,
I found one thing which might be reason of an observed behavior. The
problem does not appear for maven-based tests, while e.g. Python thin
client tests use ignite.sh for starting a cluster. So, I compared JVM
launch options and observed a following extra option in maven-based
runs:
--pat
By the way, what about Java 9? Do we run tests using it?
чт, 20 июн. 2019 г. в 13:28, Dmitriy Pavlov :
>
> Actually, TC Bot is not actively developed. I would like to say, moreover,
> help is needed there.
>
> I agree that 10095 is (intentionally) vague. Will separate notification
> based on JDK v
Actually, TC Bot is not actively developed. I would like to say, moreover,
help is needed there.
I agree that 10095 is (intentionally) vague. Will separate notification
based on JDK version be supported or not, depends on the time available to
complete this task.
чт, 20 июн. 2019 г. в 12:02, Павл
Dmitriy,
It is good to know that TC Bot is being developed actively. Just to
double check. Will the mentioned issue [1] allow us to see alerts when
a particular test fails only on a specific Java version?
[1] https://issues.apache.org/jira/browse/IGNITE-10095
чт, 20 июн. 2019 г. в 10:26, Dmitri
Hi,
About TC Bot: I was going to support filtering of builds from same JVM for
TC Bot visa
https://issues.apache.org/jira/browse/IGNITE-10095
Now it is displayed only in UI as JDK8,JDK11 tags. I still do
investigations on how to retrieve/build run history faster than it is now.
Only nightly runs
Maxim,
Well, it is an interesting point. First of all I want to believe that
issues occurring only on a specific Java version are rare. If so,
running tests on a single version for a visa should be enough.
On the other hand, a uniform test environment sounds a good idea
(especially for a visa), p
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 und
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
Hi Ivan,
Can these failures be related to Java version? Java home is set randomly by
TC Bot.
Dmitriy Pavlov
вт, 18 июн. 2019 г. в 22:11, Павлухин Иван :
> 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
12 matches
Mail list logo
