[
https://issues.apache.org/jira/browse/IGNITE-10776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16750787#comment-16750787
]
Oleg Ignatenko commented on IGNITE-10776:
-----------------------------------------
(i) note regarding possible blockers reported by TC bot above. Teamcity
currently reports that both suites fail in master exactly the same way:
[Queries 1 in
master|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Queries1&branch=pull%2F5781%2Fhead&tab=buildTypeStatusDiv&branch_IgniteTests24Java8=%3Cdefault%3E]
/ [Queries (Binary Objects Simple Mapper) in
master|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_BinaryObjectsSimpleMapperQueries&branch=pull%2F5781%2Fhead&tab=buildTypeStatusDiv&branch_IgniteTests24Java8=%3Cdefault%3E]
[~vozerov] mentioned recently in chat that it is a known problem.
As a side note, diffs for this PR show that changes made here have nothing to
do with above test suites.
> Migrate from JUnit 3 to 4 config variations test suites
> -------------------------------------------------------
>
> Key: IGNITE-10776
> URL: https://issues.apache.org/jira/browse/IGNITE-10776
> Project: Ignite
> Issue Type: Sub-task
> Affects Versions: 2.8
> Reporter: Oleg Ignatenko
> Assignee: Oleg Ignatenko
> Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This task is to migrate config variations test suites from JUnit 3 to 4.
> If needed, refer parent task comments for more details.
> Note this might be somewhat tough nut to crack design wise since
> {{JUnit4TestAdapter}} plays a special role in config variations tests, see
> IGNITE-10739.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
