playwright: [BUG] `npx playwright install` does not finish install and exits with 0
Edit from maintainers
You are affected when npx playwright install does not produce a
|■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■| 100% of XX.X Mb
line for each browser install and stops already before.
We recently see this in our CI (using playwright@1.24.2):
$ node test/unit/browser/index.js --sequential --build --browser chromium --browser webkit --tfs 'Browser Unit Tests'
browserType.launch: Executable doesn't exist at /Users/runner/Library/Caches/ms-playwright/chromium-1015/chrome-mac/Chromium.app/Contents/MacOS/Chromium
╔═════════════════════════════════════════════════════════════════════════╗
║ Looks like Playwright Test or Playwright was just installed or updated. ║
║ Please run the following command to download new browsers: ║
║ ║
║ npx playwright install ║
║ ║
║ <3 Playwright Team ║
╚═════════════════════════════════════════════════════════════════════════╝
at runTestsInBrowser (/Users/runner/work/1/s/test/unit/browser/index.js:129:48)
at /Users/runner/work/1/s/test/unit/browser/index.js:254:25 {
name: 'Error'
}
error Command failed with exit code 1.
Is this known?
//cc @pavelfeldman
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 27 (23 by maintainers)
Commits related to this issue
- devops: use debug Node.js build on CI for browser downloads (#17504) https://github.com/microsoft/playwright/issues/17394 — committed to microsoft/playwright by mxschmitt 2 years ago
- chore: download browsers out of process (#17743) https://github.com/microsoft/playwright/issues/17394 — committed to microsoft/playwright by mxschmitt 2 years ago
There is still a problem. you helped me****
We implemented like a workaround for this, it goes live in 1.27.
Please let us know if you still encounter it afterwards.
@mxschmitt Sure. Sorry if I hijacked the thread. To be clear we were seeing the downloads being stuck at 0 and then it would still report the build as a “success”. Then the tests would fail because there was no browser installed.
Here is a snippet from the machine. it was reproing consistently in CI. Let me know if you need more logs from before and after this moment.
EDIT: Later on in the pipeline we would see the following in the tests.