[test] Flaky-test: PulsarFunctionsJavaProcessTest.testTumblingCountWindowTest

[hageshiame]

Motivation

Related to issue-24843

Modifications

Verifying this change

• Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• Added integration tests for end-to-end deployment with large payloads (10MB)
• Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

• Dependencies (add or upgrade a dependency)
• The public API
• The schema
• The default values of configurations
• The threading model
• The binary protocol
• The REST endpoints
• The admin CLI options
• The metrics
• Anything that affects deployment

Documentation

• doc
• doc-required
• doc-not-needed
• doc-complete

Matching PR in forked repository

PR in forked repository:

[github-actions]

@hageshiame Please add the following content to your PR description and select a checkbox:

- [ ] `doc` <!-- Your PR contains doc changes -->
- [ ] `doc-required` <!-- Your PR changes impact docs and you will update later -->
- [ ] `doc-not-needed` <!-- Your PR changes do not impact docs -->
- [ ] `doc-complete` <!-- Docs have been already added -->

[lhotari]

It's currently hard to review this PR since the PR description isn't provided. Please provide an explanation of the changes to DockerUtils and how they relate to fixing the flaky test.

[lhotari]

Are these unrelated to the fix? Instead of adding an empty PR description, please explain the changes.

[BewareMyPower]

+1, I see some noises in recent few flaky tests related PRs, though I'm not sure whether they are really noises.