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 2019/04/01 14:20:03 UTC
[jira] [Commented] (AIRFLOW-3287) Core tests DB clean up to be run
in the right moment
[ https://issues.apache.org/jira/browse/AIRFLOW-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16806820#comment-16806820 ]
ASF subversion and git services commented on AIRFLOW-3287:
----------------------------------------------------------
Commit 1b61b95f77120d66c5e9335d49a588b209f1ad68 in airflow's branch refs/heads/v1-10-stable from Jarek
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=1b61b95 ]
[AIRFLOW-3287] Moving database clean-up code into the CoreTest.tearDown() (#4122)
> Core tests DB clean up to be run in the right moment
> ----------------------------------------------------
>
> Key: AIRFLOW-3287
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3287
> Project: Apache Airflow
> Issue Type: Improvement
> Components: core
> Reporter: Jarosław Śmietanka
> Assignee: Jarosław Śmietanka
> Priority: Minor
>
> While running a single unit test of some Dataproc operator, I've spotted that database clean-up code in `tests.core` module is triggered, which should not take place since I run unit test in a completely different place.
> A proposed solution is to move this database clean-up code inside the CoreTest as `tearDown`
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)