You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Gerardo Curiel (JIRA)" <ji...@apache.org> on 2018/08/24 06:08:00 UTC
[jira] [Commented] (AIRFLOW-2157) Builds in TravisCI are so
unstable now
[ https://issues.apache.org/jira/browse/AIRFLOW-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16591190#comment-16591190 ]
Gerardo Curiel commented on AIRFLOW-2157:
-----------------------------------------
This one can be closed [~kaxilnaik]
> Builds in TravisCI are so unstable now
> --------------------------------------
>
> Key: AIRFLOW-2157
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2157
> Project: Apache Airflow
> Issue Type: Improvement
> Components: ci, travis
> Reporter: Sergio Herrera
> Assignee: Gerardo Curiel
> Priority: Major
> Labels: CI, test
>
> At the time i write this, I have a PR that builds and pass the tests correctly. The problem is sometimes, after rebasing with changes in master branch, TravisCI builds fails because a bad environment, but after some commit recreations, it passes the tests.
> After studying some of that builds, I think the problem is that installing some things from scratch has a performance impact and other issues like unavailable services or bad packages installations.
> A possible great solution is creating a base image that contains some of the software preinstalled (e.g, databases or messages queues) as the environment for testing is the same for every build.
> This can be related to an old task (AIRFLOW-87) about creating a development environment.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)