[ https://issues.apache.org/jira/browse/IGNITE-11708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16850660#comment-16850660 ]
Ivan Pavlukhin commented on IGNITE-11708: ----------------------------------------- [~ivanan.fed], also I went through [TC results|https://ci.ignite.apache.org/viewLog.html?buildId=3969334&buildTypeId=IgniteTests24Java8_RunAllNightly] and it seems that an amount of failing test _methods_ is quite limited (roughly I counted 12). I believe that we can look into and ignore them properly. Also it might be a good idea to ask Community help to check those tests as well. > Unable to run tests in IgniteConfigVariationsAbstractTest subclasses > -------------------------------------------------------------------- > > Key: IGNITE-11708 > URL: https://issues.apache.org/jira/browse/IGNITE-11708 > Project: Ignite > Issue Type: Bug > Reporter: Ivan Fedotov > Assignee: Ivan Fedotov > Priority: Major > Labels: iep30 > Attachments: read_through_eviction_self_test.patch, > tx_out_test_fixed.patch > > Time Spent: 3h 20m > Remaining Estimate: 0h > > It seems that test classes that extend from > IgniteConfigVariationsAbstractTest cannot be started with JUnit4 @Test > annotation. > It is easy to check: if throw exception in any test methods, nothing will > happen. > Reason can be in rule chain in IgniteConfigVariationsAbstractTest class [1], > maybe it destroys existing test workflow. > [1] > https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/testframework/junits/IgniteConfigVariationsAbstractTest.java#L62 -- This message was sent by Atlassian JIRA (v7.6.3#76005)