2
0%
master: 0%

Ran 26 Apr 2016 10:04AM UTC

Files 126

Run time 6s

Badge

Embed ▾

Committed 26 Apr 2016 09:46AM UTC coverage: 66.88%. First build

Job # TOX_ENV=py27-cdh-airflow_backend_sqlite

Build Type

push

travis-ci

Committed by

bolkedebruin

Commit Message

Align start_date with the schedule_interval

This particular issue arises because of an alignment issue between
start_date and schedule_interval. This can only happen with cron-based
schedule_intervals that describe absolute points in time (like “1am”) as
opposed to time deltas (like “every hour”)

In the past (and in the docs) we have simply said that users must make
sure the two params agree. But this is counter intuitive. As in these
cases, start_date is sort of like telling the scheduler to
“start paying attention” as opposed to “this is my first execution date”.

This patch changes the behavior of the scheduler. The next run date of
the dag will be treated as "start_date + interval" unless the start_date
is on the (previous) interval in which case the start_date will be the
next run date.

Run Details

5432 of 8122 relevant lines covered (66.88%)

0.67 hits per line

airbnb / airflow / 401 / 2
0%
master: 0%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 401.2 (TOX_ENV=py27-cdh-airflow_backend_sqlite)

airbnb / airflow / 401 / 2 0% master: 0%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 401.2 (TOX_ENV=py27-cdh-airflow_backend_sqlite)

airbnb / airflow / 401 / 2
0%
master: 0%

README BADGES
x