March 2026 — OpenSearch (opensearch-project/OpenSearch) monthly summary focused on reliability and test infrastructure improvements in the OpenSearch codebase. Key accomplishments and scope: - Implemented per-test TestKit directory isolation to fix a race condition in parallel test execution, enabling reliable multi-JVM test runs when maxParallelForks > 1. - Isolated test environments by using withTestKitDir() to allocate a unique TestKit directory per test method within an already-unique TemporaryFolder, preserving daemon and task history usage for UP_TO_DATE semantics. - Fixed a NoSuchFileException and flaky failures caused by shared Groovy DSL cache under Gradle 9.4 during parallel tests, dramatically reducing intermittent CI failures. - Maintained test performance characteristics by balancing isolation with reuse of daemon/task history, ensuring faster feedback without sacrificing reliability. Impact and business value: - Significantly increased CI stability and reliability of test results, reducing debugging time and accelerating safe code changes and releases. - Reduced flaky-test related pipeline failures, enabling more predictable merge readiness and improved confidence in performance and correctness across OpenSearch components. Technology and skills demonstrated: - Gradle TestKit isolation techniques, per-test directory management, and test infrastructure hardening. - Work with Groovy-based test DSL and Java/Groovy code paths in a large-scale project. - Clear commit hygiene and effective changes to test isolation without impacting existing test semantics.