[
https://issues.apache.org/jira/browse/IGNITE-11412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814440#comment-16814440
]
Ivan Pavlukhin commented on IGNITE-11412:
-----------------------------------------
[~ivanan.fed], It seems that a little problem was introduced in this patch. It
is caused by reshuffling _rules_ execution. Currently it affects only
{{IgniteConfigVariationsAbstractTest}} subclasses. I checked an order of rules
execution (via prints) with the patch and observed a following sequence:
{code}
GridAbstractTest runRule
IgniteConfigVariationsAbstractTest rulePrivate
GridAbstractTest nameRule
{code}
And it looks really weird and completely not expected for me! And as I see
_protected_ {{GridAbstractTest#runRule}} leads us to such trouble. And I do not
like to leave it for a separate ticket because a problem was just introduced in
current one. Can we use {{nameAndRunRulesChain}} in
{{IgniteConfigVariationsAbstractTest}} to wrap it with {{rulePrivate}}? Will it
do the trick?
And if something will fail still then you can mark it with {{@Ignore}}
annotation.
> Actualize JUnit3TestLegacySupport class
> ---------------------------------------
>
> Key: IGNITE-11412
> URL: https://issues.apache.org/jira/browse/IGNITE-11412
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ivan Fedotov
> Assignee: Ivan Fedotov
> Priority: Major
> Labels: iep-30
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Specify JUnit3TestLegacySupport class documentation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
