Ash Berlin-Taylor f603b36aa4 Ensure that manually creating a DAG run doesn't "block" the scheduler (#11732) ... It was possible to "block" the scheduler such that it would not schedule or queue tasks for a dag if you triggered a DAG run when the DAG was already at the max active runs. This approach works around the problem for now, but a better longer term fix for this would be to introduce a "queued" state for DagRuns, and then when manually creating dag runs (or clearing) set it to queued, and only have the scheduler set DagRuns to running, nothing else -- this would mean we wouldn't need to examine active runs in the TI part of the scheduler loop, only in DagRun creation part. Fixes #11582		2020-10-23 09:51:03 +01:00
..
__init__.py	[AIRFLOW-6714] Remove magic comments about UTF-8 (#7338)	2020-02-02 22:18:19 +01:00
test_backfill_job.py	Use unittest.mock instead of backported mock library (#11643)	2020-10-22 13:23:15 +01:00
test_base_job.py	Use unittest.mock instead of backported mock library (#11643)	2020-10-22 13:23:15 +01:00
test_local_task_job.py	Use unittest.mock instead of backported mock library (#11643)	2020-10-22 13:23:15 +01:00
test_scheduler_job.py	Ensure that manually creating a DAG run doesn't "block" the scheduler (#11732)	2020-10-23 09:51:03 +01:00