Repository navigation
Test flake due to CPU requested in Travis CI #890
Description
Activity
/assign
minikube cpu usage is configurable using the command line flag. I haven't tested if it can work with 1 cpu
Before that, 2 cpus doesn't sound like a huge value and I'm surprised that travis ci cannot guarantee that. My assumption is that workers running in parallel can share the cpus, and most of the time we only have one job running. I wonder if we can configure the worker pool to ensure the cpus assigned to each job: https://docs.travis-ci.com/user/enterprise/worker-configuration/#configuring-the-number-of-concurrent-jobs
/assign @micw523
Sounds good. I'll do some investigations when I have time. Also let me check some of our earlier builds to see what our configurations were.
Reacted by Haowei Cai (Roy)Our previous builds were all configured for using 2 CPUs. I wonder if Travis CI had put some quota system in place.
See my personal build here.
It seems that the default config requests 2 CPUs but sometimes Travis CI only provides 1. This behavior causes Minikube to crash and the py*-functional test would fail. We should request 1 CPU from minikube instead.