Closed geoffharcourt closed 2 years ago
Whoops, looks like we deleted the env var in this PR: https://github.com/percy/cli/pull/922/files#diff-6880a3b5416b99a6e775053e1e1cb135e960f420d80f6009c6c31b2e7942cab9L72
We'll get this put back into place! v1.14 is the last version that has this for now
@Robdel12 Any idea on when the fix will be released?
Released in 1.3.0: https://github.com/percy/cli/releases/tag/v1.3.0
The problem
We upgraded to Percy CLI 1.2.1 (from 1.1.0) last night, and started seeing our browser launches start failing. We are running on Alpine Linux, which is known for being difficult to install Chrome on, and have been using our own installation for several years. We know the browser is there because our system tests are running in it, and we print the browser version out with this line right before we run the specs:
Environment
@percy/cli
version: 1.2.1Details
When our tests run, despite the local Chromium instance already being installed, we see this output:
I have confirmed by falling back to CLI v1.1.0 that this doesn't happen in that version, we end up using the specified browser and don't attempt to install or use another version of Chromium.
Debug logs
Most of the output was a successful download of Chrome, but the download part is too big to put here. This is a link the full output: https://gist.githubusercontent.com/geoffharcourt/71f9373d03a2c1c830e08ded6c3647c6/raw/a3beee21e434cac515aa6da23b9ea2bdcb284f5d/Percy%2520logs
Here's what look like the relevant parts:
Code to reproduce issue
Given the nature of testing/environment bugs, it’s best to try and isolate the issue in a reproducible repo. This will make it much easier for us to diagnose and fix.