You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/06/30 23:43:10 UTC
[jira] [Commented] (AIRFLOW-301) Unit test always fails on the last
day of the month
[ https://issues.apache.org/jira/browse/AIRFLOW-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15358055#comment-15358055 ]
ASF subversion and git services commented on AIRFLOW-301:
---------------------------------------------------------
Commit f49e238b72c1701df8ad88a0be232b6619f03edb in incubator-airflow's branch refs/heads/master from jlowin
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=f49e238 ]
[AIRFLOW-301] Fix broken unit test
This unit tests always fails on the last day of the month, since it
tries to access a nonexistent day (like June 31st).
> Unit test always fails on the last day of the month
> ---------------------------------------------------
>
> Key: AIRFLOW-301
> URL: https://issues.apache.org/jira/browse/AIRFLOW-301
> Project: Apache Airflow
> Issue Type: Bug
> Components: tests
> Affects Versions: Airflow 1.7.1.3
> Reporter: Jeremiah Lowin
> Assignee: Jeremiah Lowin
>
> The following line in the unit test for clearing XComs fails on the last day of the month:
> https://github.com/apache/incubator-airflow/blob/7980f7771ab6b6f84259ea9a52e78e4f5f690e42/tests/models.py#L560
> {code}
> ======================================================================
> ERROR: tests xcom fetch behavior with different execution dates, using
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "/home/travis/build/apache/incubator-airflow/tests/models.py", line 560, in test_xcom_pull_different_execution_date
> exec_date = exec_date.replace(day=exec_date.day + 1)
> ValueError: day is out of range for month
> -------------------- >> begin captured logging << --------------------
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)