Request 2 CPUs per Travis CI job #906
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: micw523 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/hold |
|
/hold cancel |
| setenforce 0 | ||
|
|
||
| # Request at least 2 CPUs from Travis CI per job | ||
| export TRAVIS_WORKER_DOCKER_CPUS=2 |
There was a problem hiding this comment.
I did some search and it seems the default value for TRAVIS_WORKER_DOCKER_CPUS is 2 already. I'm not sure if this is the right fix
https://github.com/travis-ci/worker/blob/b6839eb59412dd46ec2feccc85660c2afd990772/.example.env#L49-L51
https://github.com/travis-ci/worker/blob/b6839eb59412dd46ec2feccc85660c2afd990772/backend/docker.go#L60
For the original issue #890, have you observed other builds in this repo hitting the same error?
|
I also think the default is 2. The official Travis CI documentation also says at least 2 CPUs are needed to run the jobs. Nothing started flaking until a few days ago, when only 1 CPU is assigned to some of our jobs. Today’s and yesterday’s builds are fine though - I wonder if something happened on the Travis side |
|
The most recent one is from #795. For some others that were failing, I restarted the individual py-functional jobs a few times and they went green - I’m not sure if we have those records... |
|
Ok so it’s documented here - https://travis-ci.community/t/builds-often-fail-because-of-lack-of-resources-memory-cpu/4331/3 The failure is due to Travis CI. |
Add an environmental variable according to this help to avoid test flakes