Taragolis commented on PR #29035: URL: https://github.com/apache/airflow/pull/29035#issuecomment-1398808949
Just single non-relevant to this PR failure. Somehow `distributed` could avoid caplog filter: https://github.com/apache/airflow/actions/runs/3970014684/jobs/6805354398#step:6:6520 ``` with caplog.at_level(logging.ERROR, logger="airflow.jobs.backfill_job.BackfillJob"): caplog.clear() job.run() > assert "Backfill cannot be created for DagRun" in caplog.messages[0] E AssertionError: assert 'Backfill cannot be created for DagRun' in 'Failed to reconnect to scheduler after 30.00 seconds, closing client' ... ------------------------------ Captured log call ------------------------------- INFO airflow.models.dag:dag.py:2692 Sync 1 DAGs INFO airflow.models.dag:dag.py:2713 Creating ORM DAG for test_backfill_skip_active_scheduled_dagrun INFO airflow.models.dag:dag.py:3439 Setting next_dagrun for test_backfill_skip_active_scheduled_dagrun to 2016-01-01T00:00:00+00:00, run_after=2016-01-02T00:00:00+00:00 ERROR distributed.client:client.py:1312 Failed to reconnect to scheduler after 30.00 seconds, closing client ERROR airflow.jobs.backfill_job.BackfillJob:backfill_job.py:830 Backfill cannot be created for DagRun scheduled__2016-01-01T00:00:00+00:00 in 2016-01-01T00:00:00, as there's already scheduled in a RUNNING state. ERROR airflow.jobs.backfill_job.BackfillJob:backfill_job.py:837 Changing DagRun into BACKFILL would cause scheduler to lose track of executing tasks. Not changing DagRun type into BACKFILL, and trying insert another DagRun into database would cause database constraint violation for dag_id + execution_date combination. Please adjust backfill dates or wait for this DagRun to finish. ``` -- 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
