-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
trino-raptor-legacy tests are flaky, e.g. sometimes fail with OutOfMemoryError #12726
Comments
https://github.com/trinodb/trino/runs/6773580556?check_suite_focus=true
|
https://github.com/trinodb/trino/runs/6783236500?check_suite_focus=true
|
in #12730 (comment) it seems the module tests fail with roughly 40% probability (not necessarily with OOM though). this is a serious problem from CI perspective. cc @trinodb/maintainers @nineinchnick |
Side question - is it worthy to invest development time into raptor plugin? Do we know if it is used by anyone - maybe we should just remove it? |
@losipiuk Raptor is very useful for testing as it exercises the engine in ways that other connectors do not. Also, since it's standalone, it's easy to work with in integration tests. I'm utilizing it when working on the new |
No description provided.
The text was updated successfully, but these errors were encountered: