[ 
https://issues.apache.org/jira/browse/IGNITE-7538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16339443#comment-16339443
 ] 

Peter Ivanov edited comment on IGNITE-7538 at 2/9/18 1:42 PM:
--------------------------------------------------------------

Successful POC for one-build -> multi-test design was prepared in [Ignite Tests 
2.0+ \[Java 
8/9\]|https://ci.ignite.apache.org/project.html?projectId=IgniteTests20Java89] 
project. Starting work for moving and stabilization of test on the way.
*Tests*
|| Test || Java 8 || Java 9 || Comment ||
| [150 
Clients|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests20Java89_150ClientsIgniteCache150ClientsTest]
 | (/) | (?) | -- |
| 
[AOP|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests20Java89_AopIgniteAopSelfTestSuite]
 | (/) | (x) | Wait for release version which support Java 9: 
https://mvnrepository.com/artifact/org.aspectj/aspectjrt
*1.9.0.RC2*
{code}
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.092 s 
<<< FAILURE! - in org.apache.ignite.testsuites.IgniteAopSelfTestSuite
[ERROR] 
initializationError(org.apache.ignite.testsuites.IgniteAopSelfTestSuite)  Time 
elapsed: 0.018 s  <<< ERROR!
java.lang.ExceptionInInitializerError
        at 
org.apache.ignite.testsuites.IgniteAopSelfTestSuite.suite(IgniteAopSelfTestSuite.java:43)
Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess class is 
unavailable.
        at 
org.apache.ignite.testsuites.IgniteAopSelfTestSuite.suite(IgniteAopSelfTestSuite.java:43)
Caused by: java.lang.IllegalAccessException: class 
org.apache.ignite.internal.util.GridUnsafe cannot access class 
jdk.internal.misc.SharedSecrets (in module java.base) because module java.base 
does not export jdk.internal.misc to unnamed module @271053e1
        at 
org.apache.ignite.testsuites.IgniteAopSelfTestSuite.suite(IgniteAopSelfTestSuite.java:43)
{code}
*1.8.13*
{code}
AspectJ Internal Error: unable to add stackmap attributes. null
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.57 s 
<<< FAILURE! - in org.apache.ignite.testsuites.IgniteAopSelfTestSuite
[ERROR] 
initializationError(org.apache.ignite.testsuites.IgniteAopSelfTestSuite)  Time 
elapsed: 0.015 s  <<< ERROR!
java.lang.VerifyError:
Expecting a stackmap frame at branch target 10
Exception Details:
  Location:
    org/apache/ignite/gridify/BasicAopSelfTest.testAop()V @0: aload_0
  Reason:
    Expected stackmap frame at this location.
  Bytecode:
    0000000: 2ab7 0002 b800 03a7 0004 4cb1
  Exception Handler Table:
    bci [0, 7] => handler: 10

        at 
org.apache.ignite.testsuites.IgniteAopSelfTestSuite.suite(IgniteAopSelfTestSuite.java:43)
{code} |
| [Licenses & 
Javadoc|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests20Java89_LicensesJavadoc]
 | (?) | (?) | -- |


was (Author: vveider):
Successful POC for one-build -> multi-test design was prepared in [Ignite Tests 
2.0+ \[Java 
8/9\]|https://ci.ignite.apache.org/project.html?projectId=IgniteTests20Java89] 
project. Starting work for moving and stabilization of test on the way.

> Introduce new test project for Ignite 2.0+ with Java 8 / Java 9 compatibility
> -----------------------------------------------------------------------------
>
>                 Key: IGNITE-7538
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7538
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Peter Ivanov
>            Assignee: Peter Ivanov
>            Priority: Critical
>
> After IGNITE-7203 and IGNITE-6730 there are two separate test project at CI 
> which meet the problem of test configuration synchronization. It is necessary 
> to devise a solution for overcoming this issue.
> Possible approaches:
> # Single project for tests with run with different parameters.
> Problems:
> #* Test History will show history for all builds with any parameters 
> combination.
> #* Mute test will mute test for all parameters configuration.
> # Several project (differentiated by parameter) with build configuration 
> synchronisation automation.
> Problems:
> #* Maintainability — how to seamlessly support build configuration 
> synchronisation.
> Research for both approaches must be held.
> After corresponding research, following targets are required:
> # Speedup -- introduce more optimal architecture of build chain (with one 
> build - multiple tests).
> # Java 8 / Java 9 compatibility.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to