[hotfix][tests] Fix occasional pipeline E2e testcases failure #3309
+21
−61
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently,
MySqlE2eITCase
's result verification strategy is as follows: First, it keeps waiting until the last expected record received, then fetch all outputs at once and check if all expected records present.The problem is data insertion events aren't guaranteed in sequence even with single parallelism, since MySQL INSERT statements are not strictly in order. So, any records come after the "last expected record" will not be checked, causing testcases to fail.
A failed test job: https://github.com/yuxiqian/flink-cdc/actions/runs/9015394982/job/24769924116?pr=12
This PR changes the verification logic by waiting for each expected record in sequence to fix this rarely happening CI failure.