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

Extend AbstractTestQueryFramework in TestRedshiftUnload #24614

Merged
merged 1 commit into from
Jan 6, 2025

Conversation

mayankvadariya
Copy link
Contributor

Description

AbstractTestQueries was extended to cover different Trino query shapes.
However, it may not be necessary as there are query shape duplicates in
AbstractTestQueries. Additionally, AbstractTestQueries doesn't cover
different query shapes.

Additional context and related issues

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.

## Section
* Fix some things. ({issue}`issuenumber`)

@ebyhr
Copy link
Member

ebyhr commented Jan 3, 2025

/test-with-secrets sha=ca4c74e4bf05c977fe516b1d2c6f4d21d9bfa2bd

Copy link

github-actions bot commented Jan 3, 2025

The CI workflow run with tests that require additional secrets finished as failure: https://github.com/trinodb/trino/actions/runs/12594222392

@ebyhr
Copy link
Member

ebyhr commented Jan 3, 2025

Could you confirm CI failure?

Error:    TestRedshiftUnload>AbstractTestQueryFramework.init:119->createQueryRunner:72 » UnableToExecuteStatement com.amazon.redshift.util.RedshiftException: ERROR: could not open relation with OID 107333 [statement:"GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA test_schema TO alice", arguments:{}]

@mayankvadariya
Copy link
Contributor Author

@ebyhr failure is not related to code changes. Can you please restart the job?

@ebyhr
Copy link
Member

ebyhr commented Jan 4, 2025

@mayankvadariya Please investigate the cause.

@ebyhr ebyhr merged commit 2751939 into trinodb:master Jan 6, 2025
17 of 18 checks passed
@github-actions github-actions bot added this to the 469 milestone Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants