potiuk commented on PR #37524: URL: https://github.com/apache/airflow/pull/37524#issuecomment-1951441014
Cool. > Also, if a core developer can point me to the easiest way to run the relevant parts of the test suite on an M2 mac that would be wonderful ❤️ This should be rather easy : Contributing docs: https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst Particularly quick start: https://github.com/apache/airflow/blob/main/contributing-docs/03_contributors_quick_start.rst You have two options: A) Using your favourite IDE and (recommended) hatch: `hatch shell` -> will create and drop you in the right Airflow env with `[devel]` extras installed. `hatch env find` will print you where the venv is created - you can configure your IDE to use this venv and then run tests from your IDE via point/click Details: https://github.com/apache/airflow/blob/main/contributing-docs/03_contributors_quick_start.rst#setting-up-virtual-env B) using 1-1 reproducible CI dockerized environment: 1) Install pipx and do `pipx install -e ./dev/breeze` after checking out Airflow 1) `breeze ci-image build --upgrade-to-newer-dependencies` in your PR should build the container dependencies (use --help to see other options like changing python version) 2) `breeze` should use the image with docker compose command and drop you into shelll inside the docker-compose 3) then `pytest tests/io`will run io tests (you can also see the set of tests that will fail in the CI output above Details: https://github.com/apache/airflow/blob/main/contributing-docs/03_contributors_quick_start.rst#setting-up-breeze -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
