https://do.pingcap.net/jenkins/blue/organizations/jenkins/pingcap%2Ftiflow%2Fpull_syncdiff_integration_test/detail/pull_syncdiff_integration_test/815/pipeline
Observed failure from build 815:
- resumed candidate logged as `39 upperBounds= indexCode=0:1-250:0:1`
- old assertion expected a fixed resumed index pattern and failed on `first_chunk_index`
Which jobs are flaking?
pingcap/tiflow/pull_syncdiff_integration_testWhich test(s) are flaking?
sync_diff_inspector/tests/sync_diff_inspector/checkpoint/run.shlowerBoundsonly.Jenkins logs or GitHub Actions link
Anything else we need to know
lowerBoundsonly. In practice, multiple resumed chunks can share the same lower bound, so the script may pick a different valid resumed chunk and fail nondeterministically.