[jira] [Commented] (AIRFLOW-6636) Sometimes start/execution/end dates are not set for tasks (mostly in tests)
[ https://issues.apache.org/jira/browse/AIRFLOW-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17028307#comment-17028307 ] ASF subversion and git services commented on AIRFLOW-6636: -- Commit 4d6198c19fda61142618fdb5c327ced5266dc937 in airflow's branch refs/heads/master from Jarek Potiuk [ https://gitbox.apache.org/repos/asf?p=airflow.git;h=4d6198c ] [AIRFLOW-6636] Avoid exceptions when printing task instance (#7257) Sometimes (mainly in tests) tasks do not have start/execution/end date set and printing task instance information throws an exception which cover the real problems and makes diagnostics difficult. > Sometimes start/execution/end dates are not set for tasks (mostly in tests) > --- > > Key: AIRFLOW-6636 > URL: https://issues.apache.org/jira/browse/AIRFLOW-6636 > Project: Apache Airflow > Issue Type: Bug > Components: ci, tests >Affects Versions: 2.0.0, 1.10.7 >Reporter: Jarek Potiuk >Priority: Major > > Sometimes (mainly in tests) tasks do not have start/execution/end date set > and printing task instance information throws an exception which cover the > real problems and makes diagnostics difficult. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AIRFLOW-6636) Sometimes start/execution/end dates are not set for tasks (mostly in tests)
[ https://issues.apache.org/jira/browse/AIRFLOW-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17028306#comment-17028306 ] ASF GitHub Bot commented on AIRFLOW-6636: - potiuk commented on pull request #7257: [AIRFLOW-6636] Avoid exceptions when printing task instance URL: https://github.com/apache/airflow/pull/7257 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Sometimes start/execution/end dates are not set for tasks (mostly in tests) > --- > > Key: AIRFLOW-6636 > URL: https://issues.apache.org/jira/browse/AIRFLOW-6636 > Project: Apache Airflow > Issue Type: Bug > Components: ci, tests >Affects Versions: 2.0.0, 1.10.7 >Reporter: Jarek Potiuk >Priority: Major > > Sometimes (mainly in tests) tasks do not have start/execution/end date set > and printing task instance information throws an exception which cover the > real problems and makes diagnostics difficult. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AIRFLOW-6636) Sometimes start/execution/end dates are not set for tasks (mostly in tests)
[ https://issues.apache.org/jira/browse/AIRFLOW-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023833#comment-17023833 ] ASF subversion and git services commented on AIRFLOW-6636: -- Commit 79de9d30b86e99d5454abd52a19fc9f0f27c2171 in airflow's branch refs/heads/v1-10-test from Jarek Potiuk [ https://gitbox.apache.org/repos/asf?p=airflow.git;h=79de9d3 ] [AIRFLOW-6636] Avoid exceptions when printing task instance Sometimes (mainly in tests) tasks do not have start/execution/end date set and printing task instance information throws an exception which cover the real problems and makes diagnostics difficult. > Sometimes start/execution/end dates are not set for tasks (mostly in tests) > --- > > Key: AIRFLOW-6636 > URL: https://issues.apache.org/jira/browse/AIRFLOW-6636 > Project: Apache Airflow > Issue Type: Bug > Components: ci, tests >Affects Versions: 2.0.0, 1.10.7 >Reporter: Jarek Potiuk >Priority: Major > > Sometimes (mainly in tests) tasks do not have start/execution/end date set > and printing task instance information throws an exception which cover the > real problems and makes diagnostics difficult. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AIRFLOW-6636) Sometimes start/execution/end dates are not set for tasks (mostly in tests)
[ https://issues.apache.org/jira/browse/AIRFLOW-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023804#comment-17023804 ] ASF subversion and git services commented on AIRFLOW-6636: -- Commit 796b6d754fe0f9318a599e94e586edd70dfe19f3 in airflow's branch refs/heads/v1-10-test from Jarek Potiuk [ https://gitbox.apache.org/repos/asf?p=airflow.git;h=796b6d7 ] [AIRFLOW-6636] Avoid exceptions when printing task instance Sometimes (mainly in tests) tasks do not have start/execution/end date set and printing task instance information throws an exception which cover the real problems and makes diagnostics difficult. > Sometimes start/execution/end dates are not set for tasks (mostly in tests) > --- > > Key: AIRFLOW-6636 > URL: https://issues.apache.org/jira/browse/AIRFLOW-6636 > Project: Apache Airflow > Issue Type: Bug > Components: ci, tests >Affects Versions: 2.0.0, 1.10.7 >Reporter: Jarek Potiuk >Priority: Major > > Sometimes (mainly in tests) tasks do not have start/execution/end date set > and printing task instance information throws an exception which cover the > real problems and makes diagnostics difficult. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AIRFLOW-6636) Sometimes start/execution/end dates are not set for tasks (mostly in tests)
[ https://issues.apache.org/jira/browse/AIRFLOW-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023568#comment-17023568 ] ASF subversion and git services commented on AIRFLOW-6636: -- Commit a8b08e6ea25fe4986dc3b8ff3251751f3d7e96d4 in airflow's branch refs/heads/v1-10-test from Jarek Potiuk [ https://gitbox.apache.org/repos/asf?p=airflow.git;h=a8b08e6 ] [AIRFLOW-6636] Avoid exceptions when printing task instance Sometimes (mainly in tests) tasks do not have start/execution/end date set and printing task instance information throws an exception which cover the real problems and makes diagnostics difficult. > Sometimes start/execution/end dates are not set for tasks (mostly in tests) > --- > > Key: AIRFLOW-6636 > URL: https://issues.apache.org/jira/browse/AIRFLOW-6636 > Project: Apache Airflow > Issue Type: Bug > Components: ci, tests >Affects Versions: 2.0.0, 1.10.7 >Reporter: Jarek Potiuk >Priority: Major > > Sometimes (mainly in tests) tasks do not have start/execution/end date set > and printing task instance information throws an exception which cover the > real problems and makes diagnostics difficult. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AIRFLOW-6636) Sometimes start/execution/end dates are not set for tasks (mostly in tests)
[ https://issues.apache.org/jira/browse/AIRFLOW-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023526#comment-17023526 ] ASF GitHub Bot commented on AIRFLOW-6636: - potiuk commented on pull request #7257: [AIRFLOW-6636] Avoid exceptions when printing task instance URL: https://github.com/apache/airflow/pull/7257 Sometimes (mainly in tests) tasks do not have start/execution/end date set and printing task instance information throws an exception which cover the real problems and makes diagnostics difficult. --- Issue link: WILL BE INSERTED BY [boring-cyborg](https://github.com/kaxil/boring-cyborg) Make sure to mark the boxes below before creating PR: [x] - [x] Description above provides context of the change - [x] Commit message/PR title starts with `[AIRFLOW-]`. AIRFLOW- = JIRA ID* - [x] Unit tests coverage for changes (not needed for documentation changes) - [x] Commits follow "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)" - [x] Relevant documentation is updated including usage instructions. - [x] I will engage committers as explained in [Contribution Workflow Example](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#contribution-workflow-example). * For document-only changes commit message can start with `[AIRFLOW-]`. --- In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md). Read the [Pull Request Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines) for more information. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Sometimes start/execution/end dates are not set for tasks (mostly in tests) > --- > > Key: AIRFLOW-6636 > URL: https://issues.apache.org/jira/browse/AIRFLOW-6636 > Project: Apache Airflow > Issue Type: Bug > Components: ci, tests >Affects Versions: 2.0.0, 1.10.7 >Reporter: Jarek Potiuk >Priority: Major > > Sometimes (mainly in tests) tasks do not have start/execution/end date set > and printing task instance information throws an exception which cover the > real problems and makes diagnostics difficult. -- This message was sent by Atlassian Jira (v8.3.4#803005)
