[
https://issues.apache.org/jira/browse/FLINK-34963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17832089#comment-17832089
]
Ryan Skraba commented on FLINK-34963:
-------------------------------------
There's a similar compilation error in FLINK-23982 – maybe a bug in javac?!
> Compilation error in ProcessFunctionTestHarnesses
> -------------------------------------------------
>
> Key: FLINK-34963
> URL: https://issues.apache.org/jira/browse/FLINK-34963
> Project: Flink
> Issue Type: Bug
> Affects Versions: 1.20.0
> Reporter: Ryan Skraba
> Priority: Critical
> Labels: test-stability
>
>
> [https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=58627&view=logs&j=64debf87-ecdb-5aef-788d-8720d341b5cb&t=f041a596-2626-58e5-69fa-facfbaf86c0f&l=6435]
> At the compile step in *e2e_1_cron_jdk17 / Build Flink* step:
> {code:java}
> -------------------------------------------------------------
> 00:24:17.239 [ERROR] COMPILATION ERROR :
> 00:24:17.239 [INFO]
> -------------------------------------------------------------
> 00:24:17.239 [ERROR]
> /home/vsts/work/1/s/flink-streaming-java/src/test/java/org/apache/flink/streaming/util/ProcessFunctionTestHarnesses.java:[55,54]
> incompatible types: cannot infer type arguments for
> org.apache.flink.streaming.util.OneInputStreamOperatorTestHarness<>
> reason: inference variable IN has incompatible equality constraints
> OUT,IN,IN
> 00:24:17.239 [INFO] 1 error
> {code}
> This is particularly curious because *e2e_2_cron_jdk17* with an identical
> build step succeeds.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
