Skip to content

Work out why test_get_column_values_use_default.sql works locally and fails in CI #788

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

Closed
4 of 5 tasks
joellabes opened this issue May 1, 2023 · 2 comments
Closed
4 of 5 tasks
Labels
bug Something isn't working Stale triage

Comments

@joellabes
Copy link
Contributor

Describe the bug

While working on #771, I disabled integration_tests/tests/sql/test_get_column_values_use_default.sql because it was failing against all adapters but when I ran it locally (on Snowflake) it behaved correctly.

Steps to reproduce

  1. Re-enable the test
  2. Start a CI job
  3. Note that it fails
  4. Run the same integration_tests project locally
  5. Note that it succeeds

Expected results

The test to pass

Actual results

The test fails because it tries to query the table and complains that it doesn't exist, which implies that something about the load_relation() is not none logic is incorrectly claiming that the relation exists.

Screenshots and log output

06:01:16  Runtime Error in test test_get_column_values_use_default (tests/sql/test_get_column_values_use_default.sql)
06:01:16    404 Not found: Table ************:dbt_utils_integration_tests_bigquery.data_get_column_values_dropped was not found in location US
06:01:16    
06:01:16    Location: US
06:01:16    Job ID: d7ba6816-0a7d-402b-9939-6bc1a48f4a21

System information

The contents of your packages.yml file:

Which database are you using dbt with?

  • postgres
  • redshift
  • bigquery
  • snowflake
  • other (specify: ____________)

The output of dbt --version:
I think it's 1.6.0-a1 in CI, but also pretty sure I upgraded my local installation to that alpha without issue. Not 100% sure offhand.

@github-actions
Copy link

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.

@github-actions github-actions bot added the Stale label Oct 29, 2023
Copy link

github-actions bot commented Nov 5, 2023

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Stale triage
Projects
None yet
Development

No branches or pull requests

1 participant