You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running percy snapshot in my CI pipeline and it currently downloads chromium everytime. I have tried setting PERCY_BROWSER_EXECUTABLE=true but that doesn't help because npm ci deletes node_modules at the start and for yarn we don't cache node_modules but the yarn cache folder (.yarn/cache for berry).
Environment
Node version: 16
@percy/cli version: 1.0.0-beta.76
Version of Percy SDK you’re using:
If needed, a build or snapshot ID:
OS version: ubuntu
Type of shell command-line [interface]: bash
Details
There should be a global directory for caching/downloading chromium for percy. Similar to how Cypress stores it's binaries in ~/.cache/Cypress and we can cache that separately from node_modules.
For context, the Puppeteer v19.00 update moved the Chromium binary download location to ~/.cache/puppeteer (global) from the previous Puppeteer node_modules .local-chromium (local) location
Looks like Percy uses the previous .local-chromium location
The problem
I am running percy snapshot in my CI pipeline and it currently downloads chromium everytime. I have tried setting
PERCY_BROWSER_EXECUTABLE=true
but that doesn't help becausenpm ci
deletesnode_modules
at the start and for yarn we don't cachenode_modules
but the yarn cache folder (.yarn/cache
for berry).Environment
@percy/cli
version: 1.0.0-beta.76Details
There should be a global directory for caching/downloading chromium for percy. Similar to how Cypress stores it's binaries in
~/.cache/Cypress
and we can cache that separately fromnode_modules
.See cypress docs for more details: https://docs.cypress.io/guides/continuous-integration/introduction#Caching
Debug logs
First Build: https://github.com/rohit-gohri/redocusaurus/actions/runs/1975488916/attempts/1
Second Build: https://github.com/rohit-gohri/redocusaurus/runs/5526059529?check_suite_focus=true
Both of them have the logs
Code to reproduce issue
Github Workflow: https://github.com/rohit-gohri/redocusaurus/blob/56b2e916f385cdff14c5466f045370952c1f75d2/.github/workflows/e2e.yml
The text was updated successfully, but these errors were encountered: