drewsonne edited a comment on issue #4703: [AIRFLOW-3885] Improve Travis CI cycle time URL: https://github.com/apache/airflow/pull/4703#issuecomment-463538571 @BasPH as you say, each will take a long time. And the long cycle will make them longer as well. It’s a chicken and egg problem. :-) I struggle with getting work done on airflow due to the difficulty in setting up a dev environment. I still only half have a docker env like the one in the test env’s, so I end up relying on the test cases running in travis. Furthermore reading the logs to find which tests failed takes a non trivial amount of time, and then trying to figure out what more elements of the env setup I need to run a particular test take more time. The main drive of the work that I’m doing is towards your first suggestion. I’m working on the plugin architecture to split the airflow code into modular sections to let us split it out. In the meantime, it would be nice not to have to wait 2 hours if my tests passed. :-) <sub>Sent with <a href="http://githawk.com";>GitHawk</a></sub>
---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services
