You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@iceberg.apache.org by GitBox <gi...@apache.org> on 2021/01/18 02:36:32 UTC

[GitHub] [iceberg] kbendick commented on issue #2098: Spark : The iceberg-spark3-extensions module CI test failed

kbendick commented on issue #2098:
URL: https://github.com/apache/iceberg/issues/2098#issuecomment-761941085


   I too have found that this test fails. However, it does not appear to be deterministic. I'm guessing it's possible that the tests are run in such an order that the table gets dropped during one of the other tests.
   
   There's also multiple levels of inheritance used for this test suite, but I don't necessarily think that's the issue. However, it does offer some clues, as the non-abstract test suites hat inherit from the higher up classes such as `TestExtensionsTestBase` all seem to pass. The issue appears to only be in `TestCopyOnWriteDelete`, which is possibly conflicting in its `DROP TABLE` statements with the other test suite that extends `SparkRowLevelOperationsTestBase`,  `TestCopyOnWrtieMerge`, or is conflicting with tests of its own.
   
   Woud making the names of the tables used in each test somewhat random prevent this scenario? I think this would entail updating `createAndInitTable` to take in the table name and then use that table name instead of a class level variable. This is not exactly a trivial refactor though.


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

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org