Vamsi-klu commented on issue #71274: URL: https://github.com/apache/airflow/issues/71274#issuecomment-5383043065
RC testing for the `@Vamsi-klu` box on #71274. Ran on a local machine with Breeze and Docker. Official PyPI RC wheels, not this checkout's current branch. **apache-airflow==3.3.1rc2 / apache-airflow-core==3.3.1rc2** ([#70731](https://github.com/apache/airflow/pull/70731), cherry-pick of #67765) - Environment: Breeze CI image, Python 3.11.15, isolated venv, `PYTHONPATH` pointed at extracted tests only - Exact PyPI wheels `3.3.1rc2` - `apache_airflow-3.3.1rc2-py3-none-any.whl` sha256 `b52a65cc4fefc784d3a67cf55725c63e2ac4a66323277e0197b2f6b6a71ee388` - `apache_airflow_core-3.3.1rc2-py3-none-any.whl` sha256 `16454590f54b8ac1e236e973d893d4ed7c166b737791d2b6afda4112eaf6990e` - Import path: `/files/rc-older-work/venv-core/lib/python3.11/site-packages/airflow/jobs/scheduler_job_runner.py` (`site-packages`, not `/opt/airflow/airflow-core`) - `pip check`: No broken requirements found - Timeout `dagrun.duration.failed` block in that file uses `**dag_run.stats_tags` (the #70731 one-line change) - `DagRun.stats_tags` on the installed RC includes `run_type` next to `dag_id` - RC-portion tests: **3 passed in 3.17s** - I did not run the full `TestSchedulerJob` database suite. That file needs the monorepo `dag_maker` harness, and this run is against the PyPI RC, not the current branch - Result: **PASS** for the #70731 portion that is in the 3.3.1rc2 wheel 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 CORE_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]
