iammuntazirali commented on issue #60780:
URL: https://github.com/apache/doris/issues/60780#issuecomment-3916455217

   Thanks for raising this issue — I was able to reproduce it locally while 
trying to set up a development environment for contributing to the dbt-doris 
adapter.
   
   It seems there are currently two blockers preventing the adapter tests from 
running successfully:
   
   1. The `dbt-tests-adapter` package is no longer available at:
      
git+https://github.com/dbt-labs/dbt-core.git#egg=dbt-tests-adapter&subdirectory=tests/adapter
   
      and has been moved to:
      
git+https://github.com/dbt-labs/dbt-adapters.git@main#subdirectory=dbt-tests-adapter
   
      This causes installation failures when installing `dev-requirements.txt`.
   
   2. Even after updating the dependency path, test execution fails due to an 
incompatibility between:
      pytest-logbook==1.2.0
      and
      logbook>=1.9.x
   
      Recent versions of `logbook` have removed the `logbook.compat` module 
which is still imported by `pytest-logbook`, resulting in:
   
      AttributeError: module 'logbook' has no attribute 'compat'
   
   As a workaround, pinning `logbook<1.9` allows pytest to run successfully.
   
   I'm preparing a PR that:
   
   * updates the `dbt-tests-adapter` source to the new dbt-adapters repository
   * pins `logbook` to a compatible version in dev dependencies to restore test 
execution
   
   Please let me know if there’s a preferred approach for handling the 
`pytest-logbook` dependency (e.g. replacement vs version pinning).
   
   Happy to submit a PR shortly.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to