Hello, There has been, in the past, incidents where the shared Travis resource is exhausted.
It might help if you restrict to build one branch (like main) only. Some projects have acquired corporate sponsorship for a separate Travis instance. Some has moved to another system, like GitHub Action (eg superset or airflow) https://cwiki.apache.org/confluence/display/INFRA/Github+Actions+to+DockerHub (I am not certain if there is any fee involved) ASF has no policy against using other CI or test system. On Sun, Nov 8, 2020 at 11:23 AM Jia Yu <jiayu198...@gmail.com> wrote: > Hi Felix, > > I notice that recently, the Travis-CI auto-build on our PRs and commits > seem to have a very long queue time ( > https://travis-ci.org/github/apache/incubator-sedona/builds/742278311) > > Is this because we are under Apache organization and there are hundreds of > builds going on? Or is this because the build is based on a non-master > branch? If we push the commit to the master branch, will the build be > faster? > > Thanks, > Jia >
