MartijnVisser opened a new pull request, #29476:
URL: https://github.com/apache/flink/pull/29476

   ## What is the purpose of the change
   
   Bump JUnit from 5.11.4 to 5.14.4, the latest 5.x release (6.x requires Java 
17). This makes `@ParameterizedClass` available for new tests.
   
   ## Brief change log
   
     - Make private JUnit lifecycle methods in flink-runtime tests 
package-private
     - Bump `junit5.version` to 5.14.4 and implement the new `ExtensionContext` 
methods in `JUnit5TestEnvironment`
   
   ## Verifying this change
   
   This change is already covered by existing tests, such as the migration 
ITCases. On JDK 17, a dry run of the whole reactor finds the same tests on 
5.11.4 and 5.14.4, and a sample of test classes across flink-core, 
flink-runtime, the planner, the SQL gateway and flink-tests gives identical 
results on both. Regenerating the 2.3 snapshots of 
`StatefulJobWBroadcastStateMigrationITCase` with 
`MigrationTestsSnapshotGenerator` also works on both. I haven't run 
flink-yarn-tests or the other JDKs locally.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): yes
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
     - If yes, how is the feature documented? not applicable
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [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