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

   ## What is the purpose of the change
   
   Since FLINK-36336, `JavaProgramTestBase` sets object reuse on an environment 
that test programs never use, because `getExecutionEnvironment()` builds a new 
one. The object reuse variant of every subclass, and of 
`JavaProgramTestBaseJUnit4`, ran without it. `HadoopIOFormatsITCase` also 
called the wrong super method.
   
   ## Brief change log
   
     - `TestStreamEnvironment#setAsContext()` carries object reuse over to the 
environments it creates
     - Both test bases register the configured environment as context
     - Fix the super call in `HadoopIOFormatsITCase`
   
   ## Verifying this change
   
   The new `JavaProgramTestBaseITCase` fails on master: inside the job, the 
object reuse run reports `[false, false, false]`. The JUnit 4 base can't get a 
new test, so I checked it by temporarily logging the flag in 
`AvroOutputFormatITCase`. All subclasses pass locally with object reuse 
actually on. The unused `CLUSTER_OBJECT_REUSE` mode of 
`MultipleProgramsTestBase` works now too.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - 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