Node ECONNRESET error when trying to start percy

[jtmkrueger]

I'm trying to use percy-capybara, and have been struggling to get past this error.

yarn percy exec:start -v
yarn run v1.22.19
$ /app/node_modules/.bin/percy exec:start -v
[percy:config] Config file not found (0ms)
[percy:client] Creating a new build... (18ms)
[percy:env] Detected ci as null (1ms)
[percy:env] Detected commit as null (0ms)
[percy:env] Detected branch as null (0ms)
[percy:env] Detected git as {"sha":"****","branch":"****\n","message":"***","authorName":"Krueger, John","authorEmail":"***","committedAt":"2023-10-10 13:01:38 -0400","committerName":"GitHub Enterprise","committerEmail":"***"} (25ms)
[percy:env] Detected target as {"commit":null,"branch":null} (1ms)
[percy:env] Detected pullRequest as null (0ms)
[percy:env] Detected parallel as {"total":null,"nonce":null} (0ms)
[percy:env] Detected partial as false (0ms)
[percy:env] Detected info as null (0ms)
[percy:core:browser] Launching browser (612ms)
node:events:492
      throw er; // Unhandled 'error' event
      ^

Error: read ECONNRESET
    at TCP.onStreamRead (node:internal/stream_base_commons:217:20)
Emitted 'error' event on WebSocket instance at:
    at emitErrorAndClose (/dev-cache/usr/local/node_modules/ws/lib/websocket.js:1016:13)
    at ClientRequest.<anonymous> (/dev-cache/usr/local/node_modules/ws/lib/websocket.js:864:5)
    at ClientRequest.emit (node:events:514:28)
    at Socket.socketErrorListener (node:_http_client:501:9)
    at Socket.emit (node:events:514:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -104,
  code: 'ECONNRESET',
  syscall: 'read'
}

Node.js v18.17.1
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I get the same thing if I try and run it around a test

yarn percy exec -- -- rspec spec/features/u_finder_spec.rb

From what I've gathered researching, either there's a server that's not running or I'm being blocked from connecting to something.
Any help would be awesome on this!

[jtmkrueger]

I should add that I have these env vars set

# export PERCY_PROJECT=***
# export PERCY_BROWSER_EXECUTABLE="/usr/bin/chromium"
# export PERCY_TOKEN=*****

and I'm installing chromium on debian bullseye like this

apt-get install chromium-driver:arm64

[jtmkrueger]

If I remove the line from my dockerfile to install chromium-driver I get

yarn percy exec -- -- rspec spec/features/u_finder_spec.rb
yarn run v1.22.19
warning From Yarn 1.0 onwards, scripts don't require "--" for options to be forwarded. In a future version, any explicit "--" will be forwarded as-is to the scripts.
$ /app/node_modules/.bin/percy exec -- rspec spec/features/u_finder_spec.rb
[percy] Successfully downloaded Chromium 929511
[percy] Skipping visual tests
[percy] Error: Failed to launch browser. 
[qemu]: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory
...

[jtmkrueger]

I am on an m1 mac.

[itsjwala]

hey @jtmkrueger 👋

• This error is related to CLI not able to connect to the chromium browser via CDP (websocket)

• you can try circleci/node:14.18-buster-browsers-legacy following docker image which contains node as well as chromium browser.
  and set browser env like this - export PERCY_BROWSER_EXECUTABLE=$(which google-chrome)

• you can use custom docker image as well, just make sure it has chromium runtime dependencies present.
  Note: you're installing chromium-driver which seems incorrect, you'll need chromium browser installed something like this maybe apt-get install chromium-browser?

• if you're still facing issues, please reach us via support.

[jtmkrueger]

Ok, so the root of my issue was jemalloc/jemalloc#520

Once I set up a wrapper to deal with this I was able to get things working with the chromium-driver debian package.

Thanks for chiming in on this @itsjwala things are working for me now!