[ https://issues.apache.org/jira/browse/FLINK-35333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846373#comment-17846373 ]
João Boto commented on FLINK-35333: ----------------------------------- I think I resolve the problem, but on v3.1 cut the branch was not prepared for 1.19 I introduce this change on weekly workflow with the new Sink, I know I don't know if was ok.. {code:json} { flink: 1.19.0, jdk: '8, 11, 17, 21', branch: v3.1 } {code} Should we avoid add new version checks on weekly that the cut was not prepared for?? > JdbcXaSinkTestBase fails in weekly Flink JDBC Connector tests > ------------------------------------------------------------- > > Key: FLINK-35333 > URL: https://issues.apache.org/jira/browse/FLINK-35333 > Project: Flink > Issue Type: Bug > Components: Connectors / JDBC > Affects Versions: jdbc-3.2.0 > Reporter: Martijn Visser > Priority: Blocker > Labels: pull-request-available, test-stability > > https://github.com/apache/flink-connector-jdbc/actions/runs/9047366679/job/24859224407#step:15:147 > {code:java} > Error: Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:testCompile > (default-testCompile) on project flink-connector-jdbc: Compilation failure > Error: > /home/runner/work/flink-connector-jdbc/flink-connector-jdbc/flink-connector-jdbc/src/test/java/org/apache/flink/connector/jdbc/xa/JdbcXaSinkTestBase.java:[164,37] > <anonymous org.apache.flink.connector.jdbc.xa.JdbcXaSinkTestBase$1> is not > abstract and does not override abstract method getTaskInfo() in > org.apache.flink.api.common.functions.RuntimeContext > {code} -- This message was sent by Atlassian Jira (v8.20.10#820010)