jscheffl commented on PR #41067: URL: https://github.com/apache/airflow/pull/41067#issuecomment-2263686203
> > > I was thinking, does it make sense to run providers tests in DB isolation mode? We might want to skip them all? > > > > > > I actually thought it's a good idea - since we can find if our providers are doing someething like calling the DB in their code directly. Note- that we are only running db_tests (which is already quite a subset of all tests of providers - we are not running all "pure" unit tests that do not require DB - so we are limiting provider tests already. > > I see. I dont have much solution here then ^^ +1 for adding to the tests - if it blocks merging the PR I'd be okay to add it later but... yes especiually for custom operators in providers, they will break if not using internal API and iterating over the DB... or they might need to be marked as being non-compliant to databse isolation... but then would get a hard time to be migrated to Ariflow 3.0... so will be a good readiness check towards 3.0 compatability. -- 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]
