SEPURI-SAI-KRISHNA opened a new pull request, #29194:
URL: https://github.com/apache/flink/pull/29194

   ## What is the purpose of the change
   
   `testReleaseLockWhenFailedToSubmitOperation` fails on CI with a 
`RejectedExecutionException` at its final `submitOperation`. The first 
operation turns `FINISHED` on its pool thread, before that thread is back in 
the pool, and the pool hands work off through a `SynchronousQueue`. A submit 
right after `awaitOperationTermination` can therefore still find no free thread.
   
   ## Brief change log
   
   - Retry the final submit until the pool accepts it. Any other exception 
still fails the test.
   
   ## Verifying this change
   
   - With a delay injected after the first operation completes, the old test 
fails every time with the CI error, and the new test passes.
   - With the lock release on rejection removed, the new test hangs as the old 
one did, so it still guards the lock.
   - `SqlGatewayServiceITCase` passes.
   
   ## 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**
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes (please specify the tool below)
   
   Generated-by: Claude Code (Opus 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