Skip to content
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

TestPrestoNativeHiveExternalTableTpchQueriesParquet: Schema not empty: tpch #23908

Open
arhimondr opened this issue Oct 29, 2024 · 2 comments · May be fixed by #23952
Open

TestPrestoNativeHiveExternalTableTpchQueriesParquet: Schema not empty: tpch #23908

arhimondr opened this issue Oct 29, 2024 · 2 comments · May be fixed by #23952
Assignees
Labels

Comments

@arhimondr
Copy link
Member

TestPrestoNativeHiveExternalTableTpchQueriesParquet test is flaky when running on CI

[ERROR] Failures: 
[ERROR]   TestPrestoNativeHiveExternalTableTpchQueriesParquet>AbstractTestNativeHiveExternalTableTpchQueries.tearDown:117->AbstractTestQueryFramework.assertUpdate:260->AbstractTestQueryFramework.assertUpdate:265 ? Runtime Schema not empty: tpch
[INFO] 
[ERROR] Tests run: 41, Failures: 1, Errors: 0, Skipped: 0

It looks like the tpch schema is used elsewhere in other tests running concurrently with TestPrestoNativeHiveExternalTableTpchQueriesParquet. We should consider having a dedicated schema for this test if CREATE / DROP is necessary.

@arhimondr
Copy link
Member Author

CC: @agrawalreetika

@arhimondr
Copy link
Member Author

Commented out the DROP statement to unblock: https://github.com/prestodb/presto/pull/23910/files#diff-8c2b94be026fcc032d1f81fcf5382e4ad60e812816a8bb3a0a3c18f286db2c54R118

Need to uncomment once properly resolved

jxeditor pushed a commit to jxeditor/presto that referenced this issue Oct 30, 2024
@agrawalreetika agrawalreetika self-assigned this Oct 30, 2024
@agrawalreetika agrawalreetika linked a pull request Nov 5, 2024 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 🆕 Unprioritized
Development

Successfully merging a pull request may close this issue.

2 participants