-
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
Cleanup test schema in connector tests #24823
Conversation
d82cf20
to
43a2da7
Compare
try { | ||
assertUpdate("CREATE SCHEMA " + schemaName); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure why we need this change. Could you share the motivation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there were left over schema in bigquery from this test (not sure what exact CI failures) because of unproper cleanup. Over time this (and other tests being fixed here) caused a lot of schema left behind causing read timeout
in BQ intermittently while getting schema
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a real issue, not specific to tests. We should suppress a timeout failure then the schema is created remotely like #13242. Could you file an issue to track this?
...rino-bigquery/src/test/java/io/trino/plugin/bigquery/BaseBigQueryCaseInsensitiveMapping.java
Outdated
Show resolved
Hide resolved
/test-with-secrets sha=43a2da76743abe38a71c20e704167006c5ca1d96 |
The CI workflow run with tests that require additional secrets finished as failure: https://github.com/trinodb/trino/actions/runs/13020639959 |
43a2da7
to
7ec29af
Compare
I rebased on latest master. Please retrigger the CI with secrets. The failures looked unrelated |
@anusudarsan Could you confirm my review comments? |
fd3eed0
to
61a3000
Compare
done |
try { | ||
assertUpdate("CREATE SCHEMA " + schemaName); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a real issue, not specific to tests. We should suppress a timeout failure then the schema is created remotely like #13242. Could you file an issue to track this?
/test-with-secrets sha=61a3000047f33b92c498b51d03678e2267d6f8a6 |
The CI workflow run with tests that require additional secrets finished as failure: https://github.com/trinodb/trino/actions/runs/13021759543 |
@anusudarsan Could you confirm CI failure? https://github.com/trinodb/trino/actions/runs/13021759543/job/36323735412 |
61a3000
to
f5945f8
Compare
/test-with-secrets sha=f5945f8aeb01f6143a69aa80ea0b6ab51e32946b |
The CI workflow run with tests that require additional secrets finished as failure: https://github.com/trinodb/trino/actions/runs/13041977312 |
Release notes
(x) This is not user-visible or is docs only, and no release notes are required.