[
https://issues.apache.org/jira/browse/AIRFLOW-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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-NNNN]`. AIRFLOW-NNNN =
JIRA ID<sup>*</sup>
- [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).
<sup>*</sup> For document-only changes commit message can start with
`[AIRFLOW-XXXX]`.
---
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:
[email protected]
> 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)
