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

Warnings when executing integration tests #558

Closed
1 of 5 tasks
dbeatty10 opened this issue Apr 25, 2022 · 0 comments · Fixed by #581
Closed
1 of 5 tasks

Warnings when executing integration tests #558

dbeatty10 opened this issue Apr 25, 2022 · 0 comments · Fixed by #581
Labels
bug Something isn't working

Comments

@dbeatty10
Copy link
Contributor

dbeatty10 commented Apr 25, 2022

Describe the bug

When running integration tests, many warnings are printed to standard out.

Steps to reproduce

Run integration tests.

Expected results

I expected no warnings or errors.

Actual results

Before execution:

Warning: the `surrogate_key` macro now takes a single list argument instead of multiple string arguments. Support for multiple string arguments will be deprecated in a future release of dbt-utils. The dbt_utils_integration_tests.test_surrogate_key model triggered this warning. 
21:30:37  
Warning: the `surrogate_key` macro now takes a single list argument instead of multiple string arguments. Support for multiple string arguments will be deprecated in a future release of dbt-utils. The dbt_utils_integration_tests.test_surrogate_key model triggered this warning. 
21:30:37  
            Warning: the `unpivot` macro no longer accepts a `table` parameter.             This parameter will be deprecated in a future release of dbt-utils. Use the `relation` parameter instead.             The dbt_utils_integration_tests.test_unpivot_original_api model triggered this warning.             
21:30:38  [WARNING]: 'data_test_not_constant' is a seed node, but it is specified in the models
section of models/generic_tests/schema.yml. To fix this error, place the
`data_test_not_constant` specification under the seeds key instead.
21:30:38  [WARNING]: 'data_test_at_least_one' is a seed node, but it is specified in the models
section of models/generic_tests/schema.yml. To fix this error, place the
`data_test_at_least_one` specification under the seeds key instead.
21:30:38  [WARNING]: 'data_test_expression_is_true' is a seed node, but it is specified in the models
section of models/generic_tests/schema.yml. To fix this error, place the
`data_test_expression_is_true` specification under the seeds key instead.
21:30:38  [WARNING]: 'data_people' is a seed node, but it is specified in the models section of
models/generic_tests/schema.yml. To fix this error, place the `data_people`
specification under the seeds key instead.
21:30:38  [WARNING]: 'data_test_unique_where' is a seed node, but it is specified in the models
section of models/generic_tests/schema.yml. To fix this error, place the
`data_test_unique_where` specification under the seeds key instead.
21:30:38  [WARNING]: 'data_test_not_null_where' is a seed node, but it is specified in the models
section of models/generic_tests/schema.yml. To fix this error, place the
`data_test_not_null_where` specification under the seeds key instead.
21:30:38  [WARNING]: 'data_test_not_accepted_values' is a seed node, but it is specified in the
models section of models/generic_tests/schema.yml. To fix this error, place the
`data_test_not_accepted_values` specification under the seeds key instead.
21:30:38  [WARNING]: 'data_test_relationships_where_table_2' is a seed node, but it is specified in
the models section of models/generic_tests/schema.yml. To fix this error, place
the `data_test_relationships_where_table_2` specification under the seeds key
instead.
21:30:38  [WARNING]: 'data_test_mutually_exclusive_ranges_no_gaps' is a seed node, but it is
specified in the models section of models/generic_tests/schema.yml. To fix this
error, place the `data_test_mutually_exclusive_ranges_no_gaps` specification
under the seeds key instead.
21:30:38  [WARNING]: 'data_test_mutually_exclusive_ranges_with_gaps' is a seed node, but it is
specified in the models section of models/generic_tests/schema.yml. To fix this
error, place the `data_test_mutually_exclusive_ranges_with_gaps` specification
under the seeds key instead.
21:30:38  [WARNING]: 'data_test_mutually_exclusive_ranges_with_gaps_zero_length' is a seed node, but
it is specified in the models section of models/generic_tests/schema.yml. To fix
this error, place the
`data_test_mutually_exclusive_ranges_with_gaps_zero_length` specification under
the seeds key instead.
21:30:38  [WARNING]: 'data_unique_combination_of_columns' is a seed node, but it is specified in the
models section of models/generic_tests/schema.yml. To fix this error, place the
`data_unique_combination_of_columns` specification under the seeds key instead.
21:30:38  [WARNING]: 'data_cardinality_equality_a' is a seed node, but it is specified in the models
section of models/generic_tests/schema.yml. To fix this error, place the
`data_cardinality_equality_a` specification under the seeds key instead.
21:30:38  [WARNING]: 'data_test_accepted_range' is a seed node, but it is specified in the models
section of models/generic_tests/schema.yml. To fix this error, place the
`data_test_accepted_range` specification under the seeds key instead.
21:30:38  [WARNING]: 'data_not_null_proportion' is a seed node, but it is specified in the models
section of models/generic_tests/schema.yml. To fix this error, place the
`data_not_null_proportion` specification under the seeds key instead.
21:30:38  
    Warning: `dbt_utils.unique_where` is no longer supported.
    Starting in dbt v0.20.0, the built-in `unique` test supports a `where` config.
    
21:30:38  
    Warning: `dbt_utils.not_null_where` is no longer supported.
    Starting in dbt v0.20.0, the built-in `not_null` test supports a `where` config.
    
21:30:38  [WARNING]: Did not find matching node for patch with name 'test_dedupe' in the 'models' section of file 'models/sql/schema.yml'
21:30:38  [WARNING]: Test 'test.dbt_utils_integration_tests.dbt_utils_equality_test_dedupe_ref_data_deduplicate_expected_.2275e15126' (models/sql/schema.yml) depends on a node named 'test_dedupe' which was not found

During execution:

21:32:34  
Warning: the `surrogate_key` macro now takes a single list argument instead of multiple string arguments. Support for multiple string arguments will be deprecated in a future release of dbt-utils. The dbt_utils_integration_tests.test_surrogate_key model triggered this warning. 
21:32:34  
Warning: the `surrogate_key` macro now takes a single list argument instead of multiple string arguments. Support for multiple string arguments will be deprecated in a future release of dbt-utils. The dbt_utils_integration_tests.test_surrogate_key model triggered this warning. 
21:32:36  
            Warning: the `unpivot` macro no longer accepts a `table` parameter.             This parameter will be deprecated in a future release of dbt-utils. Use the `relation` parameter instead.             The dbt_utils_integration_tests.test_unpivot_original_api model triggered this warning.             
21:34:32  
    Warning: `dbt_utils.not_null_where` is no longer supported.
    Starting in dbt v0.20.0, the built-in `not_null` test supports a `where` config.
21:34:37  
    Warning: `dbt_utils.unique_where` is no longer supported.
    Starting in dbt v0.20.0, the built-in `unique` test supports a `where` config.

Screenshots and log output

image

System information

Which database are you using dbt with?

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

The output of dbt --version:

1.1.0rc2

Why it matters

  • Development could be slowed.
  • Bugs might be overlooked.

It is harder to separate the signal from the noise if there are unnecessary warnings. As a contributor, it might not be clear if the warnings are caused by the new code or existing code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant