[FLINK-39207][mysql] Fix mysql cdc could get stuck in backfill binlog reading when reuse snapshot split reader #2148
lvyanquanflink_cdc_ci.yml
on: pull_request
License Check
5m 59s
Matrix: Common Unit Tests / test
Matrix: Pipeline Unit Tests / test
Matrix: pipeline_e2e
Matrix: Source Unit Tests / test
Matrix: Source E2E Tests / test
Annotations
23 errors and 12 warnings
|
Source Unit Tests / test (11, generic, mysql-source)
Process completed with exit code 1.
|
|
Source E2E Tests / test (11, 1.19.3, source_e2e)
Process completed with exit code 1.
|
|
Pipeline Unit Tests / test (11, generic, doris, elasticsearch, fluss, hudi, iceberg, kafka, maxcompute, mysql-pipeline,...
java.lang.InterruptedException
|
|
Pipeline E2E Tests (4-Parallelism) / test (11, 1.19.3, pipeline_e2e)
YAML route block is expecting an array children, but got an OBJECT ({"source-table":"foo.bar"}). Perhaps you missed a dash prefix `-`?
|
|
Pipeline E2E Tests (4-Parallelism) / test (11, 1.19.3, pipeline_e2e)
YAML transform block is expecting an array children, but got an OBJECT ({"source-table":"foo.bar"}). Perhaps you missed a dash prefix `-`?
|
|
Pipeline E2E Tests (4-Parallelism) / test (11, 1.19.3, pipeline_e2e)
Unexpected key `transformers` in YAML route block.
|
|
Pipeline E2E Tests (4-Parallelism) / test (11, 1.19.3, pipeline_e2e)
Unexpected key `execution` in YAML top-level block.
|
|
Pipeline E2E Tests (4-Parallelism) / test (11, 1.19.3, pipeline_e2e)
Missing required field "sink-table" in route configuration
|
|
Pipeline E2E Tests (4-Parallelism) / test (11, 1.19.3, pipeline_e2e)
Missing required field "source-table" in route configuration
|
|
Pipeline E2E Tests (4-Parallelism) / test (11, 1.19.3, pipeline_e2e)
Missing required field "source-table" in transform configuration
|
|
Pipeline E2E Tests (4-Parallelism) / test (11, 1.19.3, pipeline_e2e)
One or more required options are missing.
|
|
Pipeline E2E Tests (4-Parallelism) / test (11, 1.19.3, pipeline_e2e)
Missing required field "source" in top-level configuration
|
|
Pipeline E2E Tests (4-Parallelism) / test (11, 1.19.3, pipeline_e2e)
Missing required field "sink" in top-level configuration
|
|
Pipeline E2E Tests (1-Parallelism) / test (11, 1.19.3, pipeline_e2e)
YAML route block is expecting an array children, but got an OBJECT ({"source-table":"foo.bar"}). Perhaps you missed a dash prefix `-`?
|
|
Pipeline E2E Tests (1-Parallelism) / test (11, 1.19.3, pipeline_e2e)
YAML transform block is expecting an array children, but got an OBJECT ({"source-table":"foo.bar"}). Perhaps you missed a dash prefix `-`?
|
|
Pipeline E2E Tests (1-Parallelism) / test (11, 1.19.3, pipeline_e2e)
Unexpected key `transformers` in YAML route block.
|
|
Pipeline E2E Tests (1-Parallelism) / test (11, 1.19.3, pipeline_e2e)
Unexpected key `execution` in YAML top-level block.
|
|
Pipeline E2E Tests (1-Parallelism) / test (11, 1.19.3, pipeline_e2e)
Missing required field "sink-table" in route configuration
|
|
Pipeline E2E Tests (1-Parallelism) / test (11, 1.19.3, pipeline_e2e)
Missing required field "source-table" in route configuration
|
|
Pipeline E2E Tests (1-Parallelism) / test (11, 1.19.3, pipeline_e2e)
Missing required field "source-table" in transform configuration
|
|
Pipeline E2E Tests (1-Parallelism) / test (11, 1.19.3, pipeline_e2e)
One or more required options are missing.
|
|
Pipeline E2E Tests (1-Parallelism) / test (11, 1.19.3, pipeline_e2e)
Missing required field "source" in top-level configuration
|
|
Pipeline E2E Tests (1-Parallelism) / test (11, 1.19.3, pipeline_e2e)
Missing required field "sink" in top-level configuration
|
|
Source Unit Tests / test (11, generic, mysql-source)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Common Unit Tests / test (11, generic, core)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Source E2E Tests / test (11, 1.20.3, source_e2e)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Source E2E Tests / test (11, 1.19.3, source_e2e)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Source Unit Tests / test (11, generic, postgres-source, oceanbase-source, tidb, vitess)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Source Unit Tests / test (11, generic, db2, mongodb)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Source Unit Tests / test (11, generic, oracle, sqlserver)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Pipeline Unit Tests / test (11, generic, doris, elasticsearch, fluss, hudi, iceberg, kafka, maxcompute, mysql-pipeline,...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Pipeline E2E Tests (4-Parallelism) / test (11, 1.19.3, pipeline_e2e)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Pipeline E2E Tests (1-Parallelism) / test (11, 1.20.3, pipeline_e2e)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Pipeline E2E Tests (4-Parallelism) / test (11, 1.20.3, pipeline_e2e)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Pipeline E2E Tests (1-Parallelism) / test (11, 1.19.3, pipeline_e2e)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|