automatically translate hard-coded oids in the regression tests - #3089
automatically translate hard-coded oids in the regression tests#3089zachmu wants to merge 3 commits into
Conversation
…at doltgres records
|
|
SummaryCoverage spans the core identifier translation and comparison behavior across normal flows, reconnects, retries, ordering, boundary values, and mapping updates. It also exercises adversarial and invalid-input cases, including mismatched results, conflicting identifiers, failed operations, and report generation, with the application behavior broadly healthy. Safe to merge — the only failure is an unrelated medium-severity edge case in internal report generation, and it is explicitly not attributable to this PR. No PR regressions, new failures, or previously flagged failures remain. Tests run by ItoAdditional Findings DetailsThese findings are unrelated to the current changes but were observed during testing. 🟡 Empty tracker files crash report generation
Evidence PackageTip Reply with @itoqa to send us feedback on this test run. |
|
Diff SummaryCoverage focused on business logic for translating learned object identifiers across connections and message types while preserving original diagnostics. It also exercised happy paths and edge cases around ordered result matching, invalid or partial mappings, query rewriting boundaries, connection recovery, and configurable tracker-report inputs. Safe to merge — the exercised behaviors show no PR-attributable regressions or new failures, and the implementation remains consistent across identifier translation, comparison, recovery, and reporting flows. No merge-blocking application issue was identified. Tests run by Ito
Tip Reply with @itoqa to send us feedback on this test run. |

Some regression tests use hard-coded OIDs for entities created during tests. Since doltgres assigns its own OIDs, these need to be translated for these tests to pass.