potiuk commented on issue #42632: URL: https://github.com/apache/airflow/issues/42632#issuecomment-2449671014
My proposal (high level) - it needs some detailed thinking and prototyping regarding the parallel execution of tests in CI is to follow the `breeze testing task-sdk-tests` and introduce two more testing commands: * `breeze testing provider-tests` command * `breeze testing helm-tests` command This means that we will loose some of the parallelism benefifts when we run `provider` tests and `airflow` tests together (but instead we will increase a number of jobs we have in CI, whch we still should be able to do without exceeding the limits that INFRA has on a number of parallel jobs we can run in CI jobs). So high level we will have: ## CI image bound tests: * Airflow DB tests * Airflow Non-DB Tests * TaskSDK Non-DB tests (no DB tests here) * Providers DB tests * Providers Non-DB tests ## Local virtualenv tests: * Helm Unit local virtualenv tests Likely we could also attempt to make TaskSDK tests to run in venv rather than in CI image even now - I think (@kaxil @ashb ?) there are very little dependencies there and we could easily make a local venv there instead of the whole CI image as there are no specific system or provider dependencies there. When we remove all the remaining references to providers from Airflow and Task SDK this might become: ## CI image bound tests: * Airflow DB tests * Providers DB tests * Providers Non-DB tests ## Local virtualenv tests: * Airflow Non-DB Tests * TaskSDK Non-DB tests (no DB tests here) * Helm Unit local virtualenv tests And when we add the capability of testcontainers (see #43514) that might eventually become ## CI image bound tests: * Providers DB tests * Providers Non-DB tests ## Local virtualenv tests: * Airflow DB tests * Airflow Non-DB Tests * TaskSDK Non-DB tests (no DB tests here) * Helm Unit local virtualenv tests We will still need provider tests to run in CI image and use the image to calculate constraints etc. - for quite some time (maybe for ever) but I see a clear path and stages we could take to simplify the "Airflow" and Task SDK ones. -- 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]
