Vamsi-klu commented on issue #71246: URL: https://github.com/apache/airflow/issues/71246#issuecomment-5383042955
RC testing for the `@Vamsi-klu` box on #71246. Ran on a local machine with Breeze and Docker. Official PyPI RC wheel, not this checkout's current branch. **apache-airflow-providers-google==22.3.0rc3** ([#68151](https://github.com/apache/airflow/pull/68151), issues #68040 / #68361) - Environment: Breeze CI image, Python 3.11.15, `apache-airflow==3.3.0` / `apache-airflow-core==3.3.0`, isolated venv, `PYTHONPATH` pointed at extracted tests only - Exact PyPI wheel `22.3.0rc3`, sha256 `58e34458f6a1c7e597e8a314a450bda633d4dd8e55164df6b76391010ece84b9` - Import path: `/files/rc-older-work/venv-google/lib/python3.11/site-packages/airflow/providers/google/cloud/sensors/cloud_sql.py` (`site-packages`, not `/opt/airflow/providers`) - `pip check`: No broken requirements found - Sensor class, trigger, and `CloudSQLHook.list_operations` are present on the installed RC - RC-era sensor tests from merge `dd4d2f9ef7`: **11 passed in 3.71s** - `list_operations` targetId filter: **1 passed in 3.75s** - RC-era trigger tests from the same merge: **7 passed in 3.58s** - Covered poke idle vs RUNNING/PENDING, HTTP 403/404 vs 500, deferrable execute, execute_complete, hook instance filter, trigger serialize/sleep/failure - Live Cloud SQL: skipped (no GCP project). This is the released artifact and the mocked #68151 portion, not a parallel admin workload on a real instance - Result: **PASS** Command and clock (PASS rerun, venvs already installed): ```text breeze --answer yes run --python 3.11 --skip-image-upgrade-check \ bash -lc 'export BREEZE_CONTAINER=1; bash /files/rc-older-run.sh' start_utc=2026-08-22T22:51:09Z end_utc=2026-08-22T22:51:39Z elapsed_sec=30 GOOGLE_SENSOR_PYTEST_EXIT=0 GOOGLE_HOOK_PYTEST_EXIT=0 GOOGLE_TRIGGER_PYTEST_EXIT=0 OVERALL=PASS ``` I did not tick the box from this comment. --- Drafted-by: Cursor Grok 4.6; reviewed by @Vamsi-klu before posting -- 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]
