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

route logs to dbt-core/logs instead of each test folder #4711

Merged
merged 15 commits into from
Feb 10, 2022

Conversation

emmyoop
Copy link
Member

@emmyoop emmyoop commented Feb 10, 2022

resolves #4700

Description

Logs were routing to the folders the projects were crated in. I added the log-path config to the project so that logs are all written to dbt-core/logs now, same as where they were written with the current tests.

Checklist

  • I have signed the CLA
  • I have run this code in development and it appears to resolve the stated issue
  • This PR includes tests, or tests are not required/relevant for this PR
  • I have updated the CHANGELOG.md and added information about my change

@emmyoop emmyoop requested a review from a team as a code owner February 10, 2022 20:43
@emmyoop emmyoop requested review from ChenyuLInx and iknox-fa and removed request for a team February 10, 2022 20:43
@cla-bot cla-bot bot added the cla:yes label Feb 10, 2022
@emmyoop emmyoop requested review from gshank and removed request for iknox-fa February 10, 2022 20:43
@@ -12,6 +15,8 @@

# These are the fixtures that are used in dbt core functional tests

INITIAL_ROOT = os.getcwd()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a builtin pytest fixture thing that you can use instead of this INITIAL_ROOT variable: request.config.rootdir. If you add the 'request' fixture to the signature of the 'logs_dir' fixture, that should work.

@emmyoop emmyoop requested review from gshank and removed request for a team and leahwicz February 10, 2022 21:24
@gshank
Copy link
Contributor

gshank commented Feb 10, 2022

Git seems confused because of my force push. I'm not sure what the best way to fix it is... I'd probably create a clean branch off of testing_rewrite and cherry-pick your commits onto that.

@emmyoop
Copy link
Member Author

emmyoop commented Feb 10, 2022

@gshank I seem to have resolved the conflicts.

@emmyoop emmyoop merged commit d46b197 into testing_rewrite Feb 10, 2022
@emmyoop emmyoop deleted the er/testing-rewrite-logging branch February 10, 2022 21:45
gshank added a commit that referenced this pull request Feb 19, 2022
Author: Emily Rockman <emily.rockman@dbtlabs.com>
Date:   Thu Feb 10 15:45:47 2022 -0600

    route logs to dbt-core/logs instead of each test folder (#4711)

commit 507184f
Author: Gerda Shank <gerda@dbtlabs.com>
Date:   Thu Feb 10 16:22:20 2022 -0500

    Initial pass at switching integration tests to pytest
gshank added a commit that referenced this pull request Feb 22, 2022
Author: Emily Rockman <emily.rockman@dbtlabs.com>
    route logs to dbt-core/logs instead of each test folder (#4711)

 * Initial pass at switching integration tests to pytest

* Reorganize dbt.tests.tables. Cleanup adapter handling

* Move run_sql to TestProjInfo and TableComparison.
Add comments, cleanup adapter schema setup

* Tweak unique_schema name generation

* Update CHANGELOG.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants