[rishabhdaim]

Summary

Fix a reproducible timing race in IncrementalStoreTest that caused the unrelated Elasticsearch dependency PR #3268 to fail.

Read-only stores initialize their root revision from persisted _lastRev values. The test relied on a 1 ms background writer publishing content before each reader opened; when publication lagged, the final export still contained the initial content.

Changes

• Explicitly run writer background operations after both content batches, before creating checkpoints and read-only stores.
• Disable automatic background scheduling so the test no longer depends on thread timing.
• Preserve all existing assertions and six compression/filter scenarios; no production code changes.

Validation

• Reproduced the exact CI content mismatch by disabling background scheduling and publishing only the base content.
• Ran all six IncrementalStoreTest scenarios in 20 separate Maven invocations: 120 executions, zero failures, errors or skips.
• Full oak-run module suite: 223 tests, zero failures/errors, eight skipped.
• Self-reviewed the complete diff; no additional findings.
• git diff --check passed. Spotless could not run because the project does not configure that plugin.

Links

• JIRA: https://issues.apache.org/jira/browse/OAK-12513
• Failed job: https://github.com/apache/jackrabbit-oak/actions/runs/42075556392/job/127414676101?pr=3268

Co-Authored-By: GitHub Copilot copilot@github.com

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud