jojochuang commented on PR #11779: URL: https://github.com/apache/ozone/pull/11779#issuecomment-6506186720
I reproduced the OM CI failure locally: `TestOMSnapshotCreateRequest.testEntryRenamedKeyTable` fails with expected 4 entries, actual 0. I pushed a test-only fix on top of this PR to my fork: https://github.com/jojochuang/ozone/commit/54b703089ebd8d4b638be77d8d59405c6761ff1a Branch: `jojochuang:codex/HDDS-17468-snapshot-fixture-fix`. Feel free to cherry-pick it. The fixture now commits source keys/directories in the correct tables and preserves object IDs across renames, satisfying the new committed-source guard. Its FSO DB-key helper also uses the entry's actual bucket rather than always using the first bucket. All existing assertions and production code are unchanged. Validation on JDK 21: 47 tests passed across `TestOMSnapshotCreateRequest`, `TestOMSnapshotDeleteRequest`, `TestOMKeyRenameResponse`, `TestOMKeyRenameResponseWithFSO`, and `TestOMKeysRenameResponse`; repository checkstyle passed. This fixes the deterministic OM failure; it does not address the separate Recon Derby-deadlock failure. Generated-by: Codex (GPT-6) -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
