Ajay9704 commented on PR #61347: URL: https://github.com/apache/airflow/pull/61347#issuecomment-3867293733
> > @shahar1 I tried multiple approaches to run the system tests locally, but ran into environment issues each time. The system test DAGs seem to rely on infrastructure that only exists in the CI environment (like the tests_common module, pytest setup, and GCP credentials), so I couldn’t get them working when triggering the DAGs directly from the Airflow UI. I attempted : Importing the system test DAGs directly in the Airflow UI → failed due to missing tests_common. Setting up Breeze → faced connectivity and configuration issues. Trying Docker Compose → same missing-module problems. Setting up the full GCP environment → required extensive configuration and credentials, and I kept running into blockers. I’ve been trying until now, but unfortunately I wasn’t able to run the system tests successfully. If possible, could you please guide me through the correct setup or help with running them? I’ll be happy to follow any steps you suggest. > > Screencast.From.2026-02-06.17-05-02.mp4 > > Yes - try to do it using breeze and Airflow's UI, it should be the easiest - please follow these instructions***: > > 1. Make sure that you have `gcloud` installed locally on your machine, and you're authenticated to a GCP project > > 2. Create the file `files/airflow-breeze-config/init.sh` or use the existing one, and add the following: > > > ```shell > export AIRFLOW_CONN_GOOGLE_CLOUD_DEFAULT='google-cloud-platform://' > export GOOGLE_CLOUD_PROJECT='your-gcp-project' # Fill in with GCP project ID > export SYSTEM_TESTS_GCP_PROJECT='your-gcp-project' # Fill in with GCP project ID > export SYSTEM_TESTS_ENV_ID='default' > ``` > > 3. Copy and paste the system test file to `files/dags`. > > 4. Run the test. > > 5. When you're done, copy the system test back to the original path - make sure not to commit any unwanted changes (like sensitive data). > > > *** - There are probably better ways to achieve it, but it works for me (and hopefully we could simpify it even further). If there are issues reading the `SYSTEM_TESTS_` variables, just hardcode them in the copied Dag (make sure not to commit them though). @shahar1 Thanks for reviewing the changes and for the clear guidance. I attempted to run the system tests using Breeze as instructed, but I am consistently running into an issue where the Airflow services do not start. PostgreSQL initializes successfully, but the webserver, scheduler, triggerer, and API server never come up. I reinstalled Breeze, restarted multiple times, and re-checked my environment, but the problem persists and appears to be related to my local Docker/Breeze setup. Because of this, I haven't been able to run the system tests locally. Could you advise on how to resolve this Breeze startup issue, or let me know if running system tests in CI would be acceptable for this PR? If unit tests demonstrating the behavior are sufficient, I can proceed accordingly as well. Any guidance you can provide would be very helpful. -- 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]
