Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[AIRFLOW-4661] Make airflow/config_templates Pylint compatible #6300

Merged
merged 1 commit into from
Oct 14, 2019

Conversation

arkadiuszbach
Copy link
Contributor

Make sure you have checked all steps below.

Jira

  • My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"
    • https://issues.apache.org/jira/browse/AIRFLOW-4661
    • In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.
    • In case you are proposing a fundamental code change, you need to create an Airflow Improvement Proposal (AIP).
    • In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

Description

  • Here are some details about my PR, including screenshots of any UI changes:

Tests

  • My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

  • My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
    1. Subject is separated from body by a blank line
    2. Subject is limited to 50 characters (not including Jira issue reference)
    3. Subject does not end with a period
    4. Subject uses the imperative mood ("add", not "adding")
    5. Body wraps at 72 characters
    6. Body explains "what" and "why", not "how"

Documentation

  • In case of new functionality, my PR adds documentation that describes how to use it.
    • All the public functions and the classes in the PR contain docstrings that explain what it does
    • If you implement backwards incompatible changes, please leave a note in the Updating.md so we can assign it to a appropriate release

@turbaszek
Copy link
Member

@mik-laj what do you think about the error? Does it look like a flaky test?
https://travis-ci.org/apache/airflow/builds/596117901

@mik-laj
Copy link
Member

mik-laj commented Oct 11, 2019

I restarted build.

@codecov-io
Copy link

Codecov Report

Merging #6300 into master will decrease coverage by 0.02%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #6300      +/-   ##
==========================================
- Coverage   80.41%   80.38%   -0.03%     
==========================================
  Files         612      612              
  Lines       35473    35474       +1     
==========================================
- Hits        28525    28517       -8     
- Misses       6948     6957       +9
Impacted Files Coverage Δ
airflow/config_templates/airflow_local_settings.py 80.48% <100%> (+0.48%) ⬆️
airflow/jobs/local_task_job.py 85% <0%> (-5%) ⬇️
airflow/models/taskinstance.py 93.26% <0%> (-0.51%) ⬇️
airflow/utils/dag_processing.py 56.55% <0%> (-0.35%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7c9b44d...57ddac0. Read the comment docs.

@feluelle feluelle merged commit 8cbfd93 into apache:master Oct 14, 2019
@arkadiuszbach arkadiuszbach deleted the AIRFLOW-4661 branch October 15, 2019 11:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants