kbendick commented on a change in pull request #3801:
URL: https://github.com/apache/iceberg/pull/3801#discussion_r775764402
##########
File path: core/src/test/java/org/apache/iceberg/hadoop/TestCachingCatalog.java
##########
@@ -257,6 +264,44 @@ public void
testCacheExpirationEagerlyRemovesMetadataTables() throws IOException
catalog.cache().asMap().containsKey(metadataTable)));
}
+ @Test
+ @Ignore("reproduces https://github.com/apache/iceberg/issues/3791";)
Review comment:
I figured to turn it off normally since it uses a lot of threads. I was
hoping that we might come up with a system of tagging tests as resource
intensive etc that we run nightly or something.
I've seen a handful of tests lately that start many threads and that seems
not great for CI.
But if we're ok with running this on every push, we can remove the `Ignore`.
We could either open an issue for expensive tests that we flag or hold off on
that as we might not be there yet.
But tests that spawn 20+ threads make me nervous about increasing oddities
in CI like HMS timeouts etc.
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
