lintingbin commented on PR #4185: URL: https://github.com/apache/amoro/pull/4185#issuecomment-4295628229
Gentle nudge — this fix also unblocks CI on #4180. The [recent CI run on #4180](https://github.com/apache/amoro/actions/runs/24772466254) fails with the exact pattern described in this PR's body: ``` TestInternalMixedCatalogService$CompatibilityCatalogTests.testNewCatalogLoadHistorical(boolean)[2] → IllegalStateException: update table meta failed at BasicMixedCatalog$MixedTableBuilder.createTableMeta(BasicMixedCatalog.java:404) ``` And the cascading symptoms match too — once the commit race fails once, `@After` can't drop `test_ns`, so every subsequent nested class (`TestTableCommit`, `TestTableOperation`, `TestDatabaseOperation`) fails at `.before:259` / `:186` / `:168` with `Database test_ns already exists`. Same pattern showed up on a recent master hadoop3 run ([#24488461765](https://github.com/apache/amoro/actions/runs/24488461765), 2026-04-16), confirming it's pre-existing flakiness rather than regressions introduced by the feature PRs that hit it. Would be great to get this merged so downstream CI stabilizes. -- 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]
