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 GitHub Bot (JIRA)" <ji...@apache.org> on 2018/08/26 17:27:00 UTC

[jira] [Commented] (AIRFLOW-2961) Speed up test_backfill_examples test

    [ https://issues.apache.org/jira/browse/AIRFLOW-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16592969#comment-16592969 ] 

ASF GitHub Bot commented on AIRFLOW-2961:
-----------------------------------------

Fokko opened a new pull request #3811: [AIRFLOW-2961] Refactor tests.BackfillJobTest.test_backfill_examples test
URL: https://github.com/apache/incubator-airflow/pull/3811
 
 
   Simplify this test since it takes up 15% of all the time. This is because
   every example dag, with some exclusions, are backfilled. This will put some
   pressure on the scheduler and everything. If the test just covers a couple
   of dags should be sufficient.
   
   ```
   [success] 15.03% tests.BackfillJobTest.test_backfill_examples: 254.9323s
   ```
   Make sure you have checked _all_ steps below.
   
   ### Jira
   
   - [ ] My PR addresses the following [Airflow Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
     - https://issues.apache.org/jira/browse/AIRFLOW-XXX
     - 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.
   
   ### 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](http://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [ ] In case of new functionality, my PR adds documentation that describes how to use it.
     - When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.
   
   ### Code Quality
   
   - [ ] Passes `git diff upstream/master -u -- "*.py" | flake8 --diff`
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Speed up test_backfill_examples test
> ------------------------------------
>
>                 Key: AIRFLOW-2961
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2961
>             Project: Apache Airflow
>          Issue Type: Bug
>            Reporter: Fokko Driesprong
>            Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)