danhuawang commented on PR #13050:
URL: https://github.com/apache/gravitino/pull/13050#issuecomment-5612773702

   ## Fork / private-repo IT status
   
   All CI commits for this PR are on `feat/oss-it-orchestrator` (`8730ae8`). 
There is nothing left uncommitted or unpushed.
   
   ### OSS fork (`danhuawang/gravitino`)
   
   Full `suites=all` on this head: 
https://github.com/danhuawang/gravitino/actions/runs/34376085905
   
   Passed: backend, spark, flink, maintenance, trino, access-control, 
iceberg-rest-trino, mcp, idp, multi-instance, lance-ray.
   
   Failed (product / env, not orchestrator wiring):
   
   | Suite | Cause | Issue |
   | --- | --- | --- |
   | `trino-multi-version` | Trino 478 passed; 473 `SHOW CREATE TABLE` hits 
Iceberg REST **HTTP 404** | https://github.com/apache/gravitino/issues/13068 |
   | `lance` (`lance-spark-matrix`) | 0.2.0 / 0.4.0 passed; 0.5.1 
`testCreateTableInNonExistentSchemaFails` expects `NoSuchSchemaException`, 
bundle reports `Namespace not found` | 
https://github.com/apache/gravitino/issues/13069 |
   | `python` | Hive Metastore `Connection refused` while creating a schema 
(Docker HMS not ready). Flaky env. | — |
   
   Earlier workflow-only fixes on this PR (Trino Gradle `-x` for removed Spark 
3.3/3.4/`spark-common`, multi-instance MySQL schema 2.0.0) are already in 
`8730ae8`. After that, OSS `trino` and `multi-instance` passed.
   
   ### Enterprise (`datastrato/gravitino-enterprise`)
   
   Companion PR: https://github.com/datastrato/gravitino-enterprise/pull/1862
   
   Latest enterprise `suites=all`: 
https://github.com/datastrato/gravitino-enterprise/actions/runs/34399864329
   
   Passed: backend, spark, flink, maintenance, python, trino, trino-enterprise, 
access-control, iceberg-rest-trino, mcp, idp, scim-service, scim-extension, 
search, lance-ray.
   
   Failed: `trino-multi-version` (same Trino 473 Iceberg REST 404 as #13068), 
`lance-spark-matrix` (same as #13069), `multi-instance` (enterprise-only; still 
under investigation).


-- 
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]

Reply via email to