[
https://issues.apache.org/jira/browse/IGNITE-9872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16693279#comment-16693279
]
Ignite TC Bot commented on IGNITE-9872:
---------------------------------------
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}MVCC Queries{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2352486]]
*
CacheMvccPartitionedSqlCoordinatorFailoverTest.testAccountsTxSql_Server_Backups0_CoordinatorFails
(last started)
{panel}
[TeamCity Run All
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2352486&buildTypeId=IgniteTests24Java8_MvccQueries]
> [Test falied] IgniteSinkConnectorTest.testSinkPutsWithoutTransformation
> -----------------------------------------------------------------------
>
> Key: IGNITE-9872
> URL: https://issues.apache.org/jira/browse/IGNITE-9872
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.7
> Reporter: Maxim Pudov
> Assignee: Maxim Pudov
> Priority: Major
> Fix For: 2.8
>
>
> Test started failing after updating kafka
> https://issues.apache.org/jira/browse/IGNITE-9126
> There is an issue with classloading in kafka
> https://issues.apache.org/jira/browse/KAFKA-6914, which was fixed but wasn't
> included to any public releases yet.
> It can be fixed in our test by replacing system class loader in
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest#beforeTest:
> Field scl = ClassLoader.class.getDeclaredField("scl"); // Get system class
> loader
> scl.setAccessible(true); // Set accessible
> scl.set(null, getClass().getClassLoader());
> However, it might be better to wait for kafka 1.1.2 and just update its
> version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
