It looks like grunt-ci stopped starting up on a few different prs, while it passes locally.
It might be dependency related from this:
03:04PM - 19 Aug 17 UTC
03:58AM - 31 Aug 17 UTC
CUP： Intel(R) Xeon(R) Platinum 8163 CPU @ 2.50GHz
This file has been truncated.
Chromium currently does not provide arm64 binaries for Linux. There are only
[Mac ARM with experimental support from Puppeteer](https://pptr.dev/contributing#macos-arm-and-custom-executables).
## `Cannot find module 'puppeteer-core/internal/...'`
This can occur is your Node.js version is lower than 14 or you are using a
custom resolver (such as
[`jest-resolve`](https://www.npmjs.com/package/jest-resolve)). For the former,
we do not support deprecated versions of Node.js. For the latter, usually
upgrading the resolver (or its parent module such as `jest`) will work (e.g.
## `Could not find expected browser locally`
We’re seeing the same in our other tests that use chromium. It appears to have started with the upgrade to Chromium 85 on our nodes.
@tbrisker and @ezr-ondrej did start to look into it, but so far haven’t found it. I did find this BZ from epel
Perhaps it’s the same, though a quick local check didn’t reproduce it.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-dec199d5a2 waiting in epel7-testing and perhaps that helps.