Hello everyone, We've started to experience some random failures on Travis relaated to lack of resources: those are either Out of Memory errors or lack of CPUS to run Kubernetes builds.
I tried to rerun those, thinking it was an intermittent error. It started happening yesterday and I have not seen it before so I rather doubt it is related to the latest changes. But I do not want to risk everyone being blocked so I am testing now on my own fork if reverting the latest CI changes help. I will let you know and will revert in case I found old CI works in a stable way. In the meantime - I will cancel all outstanding builds that are blocking our queue and will test it both old CI and new CI in our fork :( (Travis queue limit is not helping). Can you please hold on with rebasing/pushing new PRs until I check it. Example failures: - OSError: [Errno 12] Cannot allocate memory ( https://travis-ci.org/apache/airflow/jobs/562395978) - [ERROR NumCPU]: the number of available CPUs 1 is less than the required 2 (https://travis-ci.org/apache/airflow/jobs/562395978) J. -- Jarek Potiuk Polidea <https://www.polidea.com/> | Principal Software Engineer M: +48 660 796 129 <+48660796129> [image: Polidea] <https://www.polidea.com/>
