diqiu50 opened a new issue, #13286:
URL: https://github.com/apache/gravitino/issues/13286
### Version
main branch
### Describe what's wrong
`TestGravitinoConnector.testCatalogStatusReportsARegistrationFailure`
asserts `failure_count == 1` for a catalog whose Trino registration failed. The
`CatalogConnectorManager` load loop retries failed catalogs on every metadata
refresh (10s by default) and increments `failure_count` on each retry, so if a
refresh lands between `create_catalog` and the `catalog_status` query, the
count is already 2 and the test fails. This happens intermittently on slow CI
runners.
### Error message and/or stacktrace
```
TestGravitinoConnector446 > SingleMetalake >
testCatalogStatusReportsARegistrationFailure() FAILED
org.opentest4j.AssertionFailedError: expected: <2> but was: <1>
at
org.apache.gravitino.trino.connector.TestGravitinoConnector.testCatalogStatusReportsARegistrationFailure(TestGravitinoConnector.java:390)
```
https://github.com/apache/gravitino/actions/runs/35216070269/job/105184790131
### How to reproduce
Run TrinoIT on a loaded machine so that a metadata refresh happens between
the failed `create_catalog` call and the `catalog_status` query.
### Additional context
The retry itself is expected behavior; the test cannot pause the background
load loop.
--
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]
