question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] Error: Failed to download chromium v1000

See original GitHub issue

We have started seeing intermittent issues while trying to download Playwright in our Azure Pipelines:

yarn run v1.22.19
$ /__w/1/s/node_modules/.bin/npm-run-all -lp 'electron x64' playwright-install
[electron x64      ] $ node build/lib/electron x64
[playwright-install] $ node build/azure-pipelines/common/installPlaywright.js
[playwright-install] /__w/1/s/node_modules/playwright-core/lib/server/registry/index.js:613
[playwright-install]       throw new Error(`Failed to download ${title}, caused by\n${e.stack}`);
[playwright-install]             ^
[playwright-install] 
[playwright-install] Error: Failed to download chromium v1000, caused by
[playwright-install] Error: Client network socket disconnected before secure TLS connection was established
[playwright-install]     at connResetException (node:internal/errors:692:14)
[playwright-install]     at TLSSocket.onConnectEnd (node:_tls_wrap:1587:19)
[playwright-install]     at TLSSocket.emit (node:events:539:35)
[playwright-install]     at endReadableNT (node:internal/streams/readable:1345:12)
[playwright-install]     at processTicksAndRejections (node:internal/process/task_queues:83:21)
[playwright-install]     at /__w/1/s/node_modules/playwright-core/lib/server/registry/index.js:613:13
[playwright-install]     at async Registry._downloadExecutable (/__w/1/s/node_modules/playwright-core/lib/server/registry/index.js:612:5)
[playwright-install]     at async Registry.install (/__w/1/s/node_modules/playwright-core/lib/server/registry/index.js:590:9)
[playwright-install]     at async installBrowsersForNpmInstall (/__w/1/s/node_modules/playwright-core/lib/server/registry/index.js:780:3)
[playwright-install]     at async retry (/__w/1/s/build/azure-pipelines/common/retry.js:12:20)
[playwright-install]     at async install (/__w/1/s/build/azure-pipelines/common/installPlaywright.js:10:5)
[playwright-install] error Command failed with exit code 1.
[playwright-install] info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: "playwright-install" exited with 1.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Are there any known issues with the infrastructure hosting Playwright? Thank you!

Issue Analytics

  • State:closed
  • Created a year ago
  • Reactions:1
  • Comments:16 (12 by maintainers)

github_iconTop GitHub Comments

4reactions
s-h-a-d-o-wcommented, Sep 7, 2022

Seems like this is happening again at the moment:

Output:
Playwright build of chromium v1000 downloaded to /home/runner/.cache/ms-playwright/chromium-1000
Playwright build of ffmpeg v1007 downloaded to /home/runner/.cache/ms-playwright/ffmpeg-1007
/home/runner/work/[REDACTED]/node_modules/playwright-core/lib/server/registry/index.js:613
      throw new Error(`Failed to download ${title}, caused by\n${e.stack}`);
            ^

Error: Failed to download firefox v1322, caused by
Error: read ECONNRESET

It seems so basic that I feel silly even asking but… don’t you fetch from somewhere that has redundancy across continents?

Because at the moment, Azure seems to experience an outage only in one location:

Starting at 09:50 UTC on 07 Sep 2022, a subset of customers using Azure Cosmos DB in North Europe may experience issues accessing services.

UPDATE I suppose the outage is more severe than previously reported and spans continents… (Screenshot taken from this status page - which is a bit different than the one mentioned above)

Screenshot 2022-09-07 193837

0reactions
s-h-a-d-o-wcommented, Sep 13, 2022

As mentioned here, this probably won’t be an issue starting with 1.22.0 anymore.

@rabellino12 At least in their “next” branch, that runner now specifies the following:

playwright@^1.14.0:
  version "1.25.2"

Might be worthwhile checking whether that version is up to date in your own lockfile.

Read more comments on GitHub >

github_iconTop Results From Across the Web

ERROR: Failed to download Chromium r686378!
When utilizing Puppeteer you may intermittently encounter a build failure with the following error message: ERROR: Failed to download Chromium ...
Read more >
Playwright: “Failed to launch Browsers” — how to solve?
“Error: Failed to launch chromium because executable doesn't exist”. This post explains how to solve the above issue in the CI.
Read more >
[Ultimate PDF] Failed to launch Chromium! [0819/001522.180 ...
This error appears after we upgrade our platform version ... It is built to download a specific Chromium version, which it was tested...
Read more >
node.js - Nodejs ndb installation ERROR: Failed to download ...
Try to install ndb with this command : PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=1 sudo npm install -g ndb --unsafe-perm=true --allow-root ftw ...
Read more >
windows node_tls_reject_unauthorized - You.com | The Search ...
npm install error - unable to get local issuer certificate ... Describe the bug ... Failed to install browsers Error: Failed to download...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found