1996fanrui opened a new pull request, #29871:
URL: https://github.com/apache/flink/pull/29871

   ## What is the purpose of the change
   
   Backport of #27630 to release-2.2.
   
   ## Verifying this change
   
   - `./mvnw -pl flink-tests -am -Pskip-webui-build 
-Dtest='CheckpointIntervalDuringBacklogITCase' 
-Dsurefire.failIfNoSpecifiedTests=false package` (JDK 17), 5 runs: each `BUILD 
SUCCESS` with `Tests run: 4, Failures: 0, Errors: 0, Skipped: 1` in 
`CheckpointIntervalDuringBacklogITCase`
   - `./mvnw -q -pl flink-tests spotless:check checkstyle:check` (JDK 17): 
passed
   - Earlier, with only the first commit applied (test hardened, not ignored), 
`testNoCheckpointDuringBacklog` failed 4 of 5 runs on release-2.2 with 
`expected: 0 but was: 1`, matching FLINK-39108
   
   ## Difference from the original
   
   | Original commit | Conflict | Byte-identical | Changes |
   | --- | --- | --- | --- |
   | 0d3133b017f0 | No | Yes | None |
   | da75518e7cd7 | No | Yes | None |
   
   ## Notes
   
   - The one skipped test is `testNoCheckpointDuringBacklog`, which the second 
commit of the original PR disables with `@Ignore // FLINK-39108`, as on master. 
The other three tests of the class run and pass. The underlying bug FLINK-39108 
is not fixed on this branch.
   
   ##### Was generative AI tooling used to co-author this PR?
   
   <!--
   If generative AI tooling has been used in the process of authoring this PR, 
please
   change the checkbox below to `[X]` followed by the name of the tool, and 
uncomment the
   "Generated-by" line. See the ASF Generative Tooling Guidance for details:
   https://www.apache.org/legal/generative-tooling.html
   
   You are responsible for the quality and correctness of every change in this 
PR
   regardless of the tooling used. Low-effort AI-generated PRs will be closed. 
See
   AGENTS.md for the full guidance.
   -->
   
   - [X] Yes (please specify the tool below)
   
   Generated-by: Claude Code (Claude Opus 5.5)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to