goutamadwant opened a new pull request, #12453: URL: https://github.com/apache/seatunnel/pull/12453
### Purpose of this pull request Make `EngineStateStoreLogicalMetricExportsTest` wait for a fresh, complete logical checkpoint metrics snapshot after seeding Hazelcast-backed state. The checkpoint overview map write returns before its entry listener updates the AtomicLong counters; an immediate one-shot scrape can therefore see retained history 0 even though two entries are already in the map. This has failed CI on unrelated PRs. The fix changes only the test: it recollects the full metrics snapshot inside the existing bounded Awaitility pattern and keeps every exact expected value and backend label. It does not change production metrics, skip assertions, or increase a global timeout. ### Does this PR introduce _any_ user-facing change? No. Test synchronization only. ### How was this patch tested? - Controlled reproduction on Java 11 using the real Hazelcast event executor: with listener delivery held, the unchanged assertion failed with expected retained history 2.0 versus actual 0.0. - Same controlled schedule with the patch passed after listener delivery. The event gate was private verification instrumentation and is not in this PR. - Final gate-free focused run passed: `EngineStateStoreLogicalMetricExportsTest` and `HazelcastCheckpointOverviewStateStoreTest` (3 tests, 0 failures/errors/skips). - Spotless and `git diff --check` passed. Full CI, Java 8, and native Windows remain for the hosted checks. ### Check list * [ ] New Jar license notice: not applicable. * [ ] Documentation: not applicable; no user-facing behavior change. * [ ] incompatible-changes.md: not applicable. * [ ] Connector registration, distribution, CI label, E2E, and plugin config: not applicable; no connector code changed. -- 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]
