Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Failed to launch the browser process! spawn C:\npm\prefix\node_modules\puppeteer\.local-chromium\win64-737027\chrome-win\chrome.exe ENOENT #42

Closed
CAMOBAP opened this issue Apr 27, 2020 · 5 comments
Assignees

Comments

@CAMOBAP
Copy link
Contributor

CAMOBAP commented Apr 27, 2020

https://github.com/metanorma/mn-samples-un/pull/35/checks?check_run_id=611650211

@CAMOBAP CAMOBAP self-assigned this Apr 27, 2020
CAMOBAP added a commit that referenced this issue Apr 27, 2020
@CAMOBAP CAMOBAP mentioned this issue Apr 27, 2020
CAMOBAP added a commit that referenced this issue Apr 27, 2020
@CAMOBAP
Copy link
Contributor Author

CAMOBAP commented Apr 27, 2020

During installation there is a strange line System.Management.Automation.RemoteException

@CAMOBAP
Copy link
Contributor Author

CAMOBAP commented Apr 27, 2020

Previously we also had this line in past CI runs

@CAMOBAP
Copy link
Contributor Author

CAMOBAP commented Apr 28, 2020

Can be related to this puppeteer/puppeteer#5745

@CAMOBAP
Copy link
Contributor Author

CAMOBAP commented Apr 28, 2020

At this point looks like downgrading to 2.1.1 the only option

CAMOBAP added a commit that referenced this issue Apr 28, 2020
@CAMOBAP
Copy link
Contributor Author

CAMOBAP commented Apr 28, 2020

Fixed with restriction of node 14, will be available in next release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant