Yarn cache has problems for ~10% of deploys

** Please describe which feature you have a question about? **
I seem to run into deployment problems with yarn's cache, only when doing console deploys, and usually for a different package each time. The last few are below.

I don't have caching turned on in build settings, or any other exotic configuration, just running yarn install in the build step causes these issues. Is there a setting I can enable so this doesn't occur?

Also, the build email notifications are not helpful, I don't need my inbox filled with emails for each build, I only need emails in case of failure

It wouldn't be so frustrating if the whole deploy cycle didn't take 20 minutes, and these failures are in the frontend build, 16 minutes into the process, even when there are no backend changes.

** Provide additional details**
error An unexpected error occurred: "ENOENT: no such file or directory, open '/usr/local/share/.cache/yarn/v4/npm-retry-0.12.0-1b42a6266a21f07421d1b0b54b7dc167b01c013b/node_modules/retry/.yarn-metadata.json'".
2020-01-23T12:34:33.167Z [INFO]: info If you think this is a bug, please open a bug report with the information provided in "/codebuild/output/src052057409/src/s12/src/yarn-error.log"

2020-01-22T16:18:07.662Z [WARNING]: error https://registry.yarnpkg.com/json-buffer/-/json-buffer-3.0.0.tgz: Extracting tar content of undefined failed, the file appears to be corrupt: "ENOENT: no such file or directory, stat '/usr/local/share/.cache/yarn/v4/npm-json-buffer-3.0.0-5b1f397afc75d677bde8bcfc0e47e1f9a3d9a898/node_modules/json-buffer/LICENSE'"

2020-01-22T14:01:37.278Z [WARNING]: error https://registry.yarnpkg.com/@babel/runtime/-/runtime-7.3.1.tgz: Extracting tar content of undefined failed, the file appears to be corrupt: "ENOENT: no such file or directory, chmod '/usr/local/share/.cache/yarn/v4/npm-@babel-runtime-7.3.1-574b03e8e8a9898eaf4a872a92ea20b7846f6f2a/node_modules/@babel/runtime/helpers/esm/newArrowCheck.js'"

2020-01-20T14:38:37.282Z [WARNING]: error https://registry.yarnpkg.com/@babel/runtime/-/runtime-7.3.1.tgz: Extracting tar content of undefined failed, the file appears to be corrupt: "ENOENT: no such file or directory, chmod '/usr/local/share/.cache/yarn/v4/npm-@babel-runtime-7.3.1-574b03e8e8a9898eaf4a872a92ea20b7846f6f2a/node_modules/@babel/runtime/helpers/esm/toPropertyKey.js'"

2020-01-23T14:41:12.800Z [WARNING]: error https://registry.yarnpkg.com/array-includes/-/array-includes-3.0.3.tgz: Extracting tar content of undefined failed, the file appears to be corrupt: "ENOENT: no such file or directory, chmod '/usr/local/share/.cache/yarn/v4/npm-array-includes-3.0.3-184b48f62d92d7452bb31b323165c7f8bd02266d/node_modules/array-includes/.travis.yml'"

Start by reviewing the console deploy build step that runs yarn install and the errors in /codebuild/output/src052057409/src/s12/src/yarn-error.log. Reproduce the intermittent cache extraction failures and determine whether the build email notification behavior is part of the same work; done means the reported deploy failures and requested notification behavior have clear, verified outcomes.

Written by the indexing model from the issue text.