Request 2 CPUs per Travis CI job

[micw523]

Add an environmental variable according to this help to avoid test flakes

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: micw523
To complete the pull request process, please assign yliaog
You can assign the PR to them by writing /assign @yliaog in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[micw523]

/hold
Need to see if CI likes it

[micw523]

/hold cancel
/assign @roycaihw
Looks OK on my personal build.

[roycaihw]

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?

[micw523]

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

[micw523]

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...

[micw523]

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.