[
https://issues.apache.org/jira/browse/FLINK-13528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900846#comment-16900846
]
Chesnay Schepler commented on FLINK-13528:
------------------------------------------
Handling this in the user-jar is a relatively complicated solution.
When you return from a progrem that is submitted via a CLI without triggering a
job, then the CLI will actually throw an exception.
We'd have to modify the test to
a) ignore this exception when it occurs in the logs
b) detect that the CLI invocation failed with this exception and handle it
gracefully.
I'd handle this case like we handled Java 9 exclusions; guard the actual call
to the test with a either a JDK check or property.
Something like
{code}
if [[ ${PROFILE} != *"jdk11"* ]]; then
run_test "Kafka 0.10 end-to-end test"
"$END_TO_END_DIR/test-scripts/test_streaming_kafka010.sh"
run_test "Kafka 0.11 end-to-end test"
"$END_TO_END_DIR/test-scripts/test_streaming_kafka011.sh"
fi
{code}
As for other test exclusions, my plan is to disable the maven-surefire-plugin
for modules that categorically fail (hbase, hive), and use a jUnit category for
specific tests if the feature isn't broken in general (possibly cassandra) or
(hopefully) temporary (FLINK-13515, FLINK-13516).
Note that I also plan to remove the jdk9 profile _entirely_ once we arrived at
a comparable state, which we aren't that far from. The above mechanism should
overall introduce little noise; much less so that we had for Java 9.
> Kafka 0.10/0.11 E2E test fail on Java 11
> ----------------------------------------
>
> Key: FLINK-13528
> URL: https://issues.apache.org/jira/browse/FLINK-13528
> Project: Flink
> Issue Type: Sub-task
> Components: Connectors / Kafka, Tests
> Reporter: Chesnay Schepler
> Priority: Major
> Fix For: 1.10.0
>
>
> The kafka 0.10/0.11 E2E tests fail on Java 11 with a timeout. Since kafka
> added support for Java 11 in 2.1.0 we may have to just disable them.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
