geyanggang opened a new issue, #10235:
URL: https://github.com/apache/gravitino/issues/10235

   ### Version
   
   main branch
   
   ### Describe what's wrong
   
   Two flaky test failures occur intermittently in CI:
   1. Web-v2 integration test fails with StaleElementReferenceException when 
verifying tree nodes after page refresh
   2. Trino connector integration test fails with HDFS write errors due to 
DataNode not being fully ready
   Both issues are timing-related and occur more frequently in CI environments.
   
   
   ### Error message and/or stacktrace
   
   1. Web-v2 test error:
   org.openqa.selenium.StaleElementReferenceException: stale element reference: 
stale element not found in the current frame
   at 
org.apache.gravitino.integration.test.web.ui.pages.CatalogsPage.verifyTreeNodes(CatalogsPage.java:1622)
   at 
org.apache.gravitino.integration.test.web.ui.CatalogsPageTest.testRefreshSchemaPage(CatalogsPageTest.java:430)
   
   2. Trino test error:
   org.apache.hadoop.ipc.RemoteException: File 
/user/iceberg/warehouse/TrinoQueryIT/gt_db2/tb01/metadata/00001-*.metadata.json 
could only be written to 0 of the 1 minReplication nodes. There are 1 
datanode(s) running and no node(s) are excluded in this operation.
   Caused by: java.lang.IllegalArgumentException: Self-suppression not permitted
   at 
org.apache.iceberg.TableMetadataParser.$closeResource(TableMetadataParser.java:131)
   
   
   ### How to reproduce
   
   1. For web-v2 test: Run `./gradlew :web-v2:integration-test:test` multiple 
times in CI environment
   2. For Trino test: Run `./gradlew :trino-connector:integration-test:test` in 
CI environment where HDFS containers may not be fully initialized
   
   
   ### Additional context
   
   _No response_


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