suryaprasanna opened a new pull request, #18207: URL: https://github.com/apache/hudi/pull/18207
### Describe the issue this Pull Request addresses Flaky memory regressions are often triggered by environment/runtime changes (JVM, CI container limits, or test runner behavior), not only by code changes. Diagnosing these regressions is difficult when test logs do not include runtime memory context. This PR adds a lightweight unit test that reports JVM memory statistics during test execution to improve observability when investigating memory-related regressions. ### Summary and Changelog - Added `TestReportJvmConfiguration` under `hudi-common` tests. - The test logs heap and non-heap memory metrics using `MemoryMXBean`. - The test also logs runtime memory metrics (`total`, `free`, `used`) via `Runtime` APIs. - The goal is diagnostic visibility in CI/local logs for environment comparison during flaky memory investigations. ### Impact - Improves debugging signal for memory regressions by providing consistent JVM memory snapshots in test logs. - No functional behavior change in production code paths. - Minimal runtime overhead since this is a single lightweight test utility. ### Risk Level low This is test-only, additive, and non-invasive. ### Documentation Update none ### Contributor's checklist - [x] Read through [contributor's guide](https://hudi.apache.org/contribute/how-to-contribute) - [x] Enough context is provided in the sections above - [x] Adequate tests were added if applicable Made with [Cursor](https://cursor.com) -- 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]
