You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mikhail Petrov (Jira)" <ji...@apache.org> on 2021/01/17 16:15:00 UTC
[jira] [Updated] (IGNITE-14007) Ignite-extensions: ignite-kafka
integration test causes TC build failure
[ https://issues.apache.org/jira/browse/IGNITE-14007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Petrov updated IGNITE-14007:
------------------------------------
Summary: Ignite-extensions: ignite-kafka integration test causes TC build failure (was: Ignite-extensions: ignite-kafka integration test suite fails TC build)
> Ignite-extensions: ignite-kafka integration test causes TC build failure
> ------------------------------------------------------------------------
>
> Key: IGNITE-14007
> URL: https://issues.apache.org/jira/browse/IGNITE-14007
> Project: Ignite
> Issue Type: Bug
> Reporter: Mikhail Petrov
> Assignee: Mikhail Petrov
> Priority: Major
>
> JVM exits with code 130 during ignite-kafka-ext:IgniteSourceConnectorTest execution that causes TC build failure - [TC build|https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Build/5831371?showLog=5831371_14949_1587.14949&logFilter=debug]
> It happens because
> 1. Started in FlinkIgniteSunkSelfTest ignite instance remains unclosed. And since it s started in separate test suite it is not closed automatically by Ignite test framework since maven surefire plugin uses different classloaders to load classes from different test suites.
> 2. Extra node causes error in marshalling of remote event filter because of [IGNITE-14006|https://issues.apache.org/jira/browse/IGNITE-14006]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)